From: Junio C Hamano Date: Thu, 02 Feb 2012 19:13:32 GMT Subject: Re: Finding all commits which modify a file Message-ID: <7vk445vyjn.fsf@alter.siamese.dyndns.org> In-Reply-To: <5456.38.96.167.131.1328194547.squirrel@mail.lo-cal.org> "Neal Groothuis" writes: >> "Neal Groothuis" 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? Yes. In case my tongue-in-cheek comment was too obscure, I was saying that I do not think the change to TREESAME-ness check you were alluding to would break any use case I would think of off the top of my head. We of course might discover undesired consequences in unexpected corners after we try your change, but I do not think we can discuss such corner cases further without seeing a patch.