Re: [PATCH] describe: output tag's ref instead of embedded name
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 20, 2020, 22:59 UTC
- Message-ID
- <xmqqftf49862.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <CAHd-oW7HJb2d10U_dcbB6G-UdopQ7HKyghAji=9VhmAgn3Dw_Q@mail.gmail.com>
Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:
> I now this is just an illustration, but shouldn't this example be "git > describe --contains v1.0-bob~1"?
No, none of the patches discussed in this thread would not affect anything in --contains (as it is a completely different program). The example was bad to use one commit _before_; I meant to use one commit _after_ the tag.
> Another case that came to my mind is when the user runs `git describe > --abrev=0 HEAD` and v1.0-bob points to HEAD~. In this case, v1.0 will > be displayed without suffix,...
In this case, v1.0-1- is followed by the full object name, I think.