Re: history damage in linux.git
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 21, 2016, 16:59 UTC
- Message-ID
- <xmqqzismsxsu.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CA+55aFx8hPKKcuwe-HHoO7LHVYLmJ6khndd-OtQotMs3EJzZ0w@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 5 quoted lines
> That commit aed06b9 can also be described as > > v3.13-rc7~9^2~14^2~42 > > so describing it as 'v4.6-rc1~9^2~792' is clearly not closer in any way.
I seem to recall that name-rev had an unexplained heuristics to strongly avoid following second parent changes (I see two ^2 in the path from 3.13-rc7 above).
Show 5 quoted lines
> However did git decide to use that further-away name? That looks odd. > > I'm wondering if it's because of the new root commit we have, and that > confuses the distance calculation somehow? That came in somewhat > recently (mid March) with the GPIO pull.