> "Neal Groothuis" <ngroot@xxxxxxxxxx> writes: > >> Is there a situation where checking for TREESAMEness before >> simplification >> is desirable and checking after would not be? > > When you do not want to see a side branch that does not contribute to the end result at all, obviously ;-). Outside that situation, before or after should not make a difference, I would think. In that case, you wouldn't be using the --full-history flag at all, yeah? Right now, we can see where the file gets changed (A1), we just can't see where it gets changed back (B2). In fact, if I run git-log --full-history --simplify-merges foo.txt, it looks like A1 was the last thing to make changes to foo.txt, which seems misleading to me---history has been simplified to the point of not being true. -- 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