Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Finding all commits which modify a file

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:52:55

"Neal Groothuis" [off-list ref] writes:
quoted
"Neal Groothuis" [off-list ref] writes:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help