Re: [PATCH] describe: output tag's ref instead of embedded name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Matheus Tavares Bernardino <matheus.bernardino@xxxxxx> 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.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux