Re: bug in 'git describe'?

From: Sebastian Kuzminsky <seb@highlab.com>
Date: Sep 25, 2018, 15:39 UTC
Message-ID: <dbd2dcef-c892-3628-119e-f688e74f3599@highlab.com>
In-Reply-To: <xmqqefdir0tz.fsf@gitster-ct.c.googlers.com>

On 9/24/18 4:24 PM, Junio C Hamano wrote:

Show 9 quoted lines

> Sebastian Kuzminsky <seb@highlab.com> writes:
> 
>> I've got two tiny git repos whose commit graphs are identical, but 
>> where 'git describe' gives different results. ... The histories
>> differ only in the timestamps of the commits...
> 
> describe does take the commit timestamps into account, so it is 
> expected you would get different results out of an otherwise 
> identically looking graph.

Thanks for that confirmation.

That behavior seems to me to be different from what the (2.11) manpage says:

> it suffixes the tag name with the number of additional commits on top
> of the tagged object

And:

Show 5 quoted lines

> If multiple tags were found during the walk then the tag which has
> the fewest commits different from the input commit-ish will be
> selected and output. Here fewest commits different is defined as the
> number of commits which would be shown by git log tag..input will be
> the smallest number of commits possible.

All that said, if you consider this "working as expected" then i'm content to let the matter drop.

-- 
Sebastian Kuzminsky