Re: bug in 'git describe'?

From: Duy Nguyen <pclouds@gmail.com>
Date: Sep 25, 2018, 16:05 UTC
Message-ID: <CACsJy8C4+cj=K2NetC05rmwenY0cArQ7NehZZ+Df90fmzBVThA@mail.gmail.com>
In-Reply-To: <dbd2dcef-c892-3628-119e-f688e74f3599@highlab.com>

On Tue, Sep 25, 2018 at 5:41 PM Sebastian Kuzminsky <seb@highlab.com> wrote:

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

Good opportunity to improve the man page anyway even if Junio is right. I agree that the section about "search strategy" is a bit misleading because it does not mention anything about time stuff.

Show 12 quoted lines

>
> > it suffixes the tag name with the number of additional commits on top
> > of the tagged object
>
>
> And:
>
> > 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.

-- 
Duy