Re: bisect / history preserving on rename + update
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 25, 2007, 17:23 UTC
- Message-ID
- <7vd4xb5y12.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.LFD.0.999.0708250819360.25853@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 6 quoted lines
>> It was corrected into the current behaviour, following the guiding >> principle described in this message: >> >> http://thread.gmane.org/gmane.comp.version-control.git/3807 > > Ahh, you're a wily one. Using my own words against me.
I am not being wily. I usually do not remember nor quote too old histories, but June 2005 was somewhat special to me. Those two weeks of 18-hour-straight-doing-git-and-nothing-else, working with git and with you in particular, were what taught me how fun open source development and working with brilliant others is.
> Ie, the true "guiding principle" should be the principle of minizing the > final diff - that's how diff is supposed to act within a single file, and > I think it's how the rename/copy detection is supposed to act too.
Ok, I would agree with that in principle, but that would be rather intrusive change that I am sure would have fallout to git-apply side (and anybody who interprets "git diff" output, especially gitweb), too. I am not rejecting the idea, but I won't be able to look into it myself for some time.