Junio C Hamano <gitster@xxxxxxxxx> writes: > The idea is to compute, for each commit in the "full history" result set, > the commit that should replace it in the simplified history. This > replacement commit is defined as follows: > > * In any case, we first figure out the replacement commits of parents of > the commit we are looking at. The commit we are looking at is > rewritten as if its parents are replacement commits of its original > parents. > > * If the commit is marked as TREESAME (i.e. it modifies the paths we are > interested in), then the replacement commit is itself. IOW, the commit > is not dropped from the final result. A typo here. This comment should have said !TREESAME (the code is correct). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
