Re: [PATCH 0/5] activate diff.renames by default
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 23, 2016, 21:40 UTC
- Message-ID
- <xmqqsi0jxfz8.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <vpqsi0jf94g.fsf@anie.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 25 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > >> Matthieu Moy <Matthieu.Moy@imag.fr> writes: >> >>> I have always wondered why diff.renames was not activated by default. >>> I've had it to true in my configuration for 9 years, and I've been >>> teaching newbies to set it for a while without issue. I think it's >>> time to activate it by default, but please let me know if I missed a >>> reason to keep it to false. >>> >>> In any case, the first 3 patches are useful cleanups. >> >> It's a long time coming since I heard "I love how I can just say >> 'oh, keep in mind that we might want to..' and 24 hours later you >> did it." [*1*] >> >> I can hardly be an impartial judge for this series, though. >> >> [Reference] >> >> *1* http://thread.gmane.org/gmane.comp.version-control.git/3541/focus=3702 > > I guess there's another reference needed to fully understand your > message, and I'm not sure I have it right. Are you refering to the > "merge-recursive: test rename threshold option" discussion?
Not at all.
I was just mentioning that it would at last be a major achievement, if this can safely turned on by default for everybody, after having invented the machinery and the feature looooong time ago ;-)