Re: feature "git tag -r" to show tags and commits they are pointing to
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 22, 2009, 21:35 UTC
- Message-ID
- <7vr5svf6x9.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <76c5b8580910221424n220449b9vda26f032174b6fa7@mail.gmail.com>
Eugene Sajine <euguess@gmail.com> writes:
Show 26 quoted lines
> Hi, > > Currently there is no way you can get the commits your tags are > pointing to by using git tag. > The only way i found is to use rev-parse (which is by the way not > supported by the bash_completion) > > It seems reasonable to have upper level command like: > > $ git tag -r > > to output > > v0.1 8794hke84f9e8h9ef9eh949793... > v0.2 jhkd934398e9f499f47w9789o97... > > $ git tag -n -r > > v0.1 "super message" 8794hke84f9e8h9ef9eh949793... > v0.2 "another message" jhkd934398e9f499f47w9789o9f... > > $ git tag -r v0.2 > v0.2 jhkd934398e9f499f47w9789o9f... > > > What do you think?
Not intereseted at all, as this does not look anything more than "because I could", not "because this is useful and sorely lacking".
The "super message" and such are actually useful to humans, but "v0.1" is much more useful than 8794hke to humans, and these tag names are just as usable as the hexadecimal commit object names to the tools. You can say "git show v0.1^0" and "git show 8794hke" and get the same thing.
Heck, "8794hke" is not even hexadecimal, and the fact that you did not even notice it is a _S*RE_ sign that they are not useful to humans.
If you _are_ a human, that is ;-)
In other words, please do not justify such a proposal with "I want to have 'git tag' command to show the commit object name". Rather, justify _why_ (1) you _need_ to show the commit object name to begin with, and (2) the output _has_ to come from 'git tag' and not 'git rev-parse'.