From: Junio C Hamano <gitster@pobox•com>
To: Jan Engelhardt <jengelh@computergmbh•de>
Cc: git@vger•kernel.org
Subject: Re: git-describe only works on full tags
Date: Sun, 16 Mar 2008 19:13:09 -0700 [thread overview]
Message-ID: <7vhcf6cd3e.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0803170137300.14822@fbirervta.pbzchgretzou.qr> (Jan Engelhardt's message of "Mon, 17 Mar 2008 01:41:03 +0100 (CET)")
Jan Engelhardt <jengelh@computergmbh•de> writes:
> For some reason, git-describe only prints a description relative to
> the last tag that was a tag object (and not just a ref).
> This is kinda a bug to me, what do others think?
There is an option to tell git-describe to allow using non annotated
tags, but that is not a defult.
This is a very deliberate design decision. Annotated tags are meant for
public consumption, but lightweight tags are often used to locally mark
points that are interesting during this current development session
(e.g. "I am trying to improve by first breaking and then enhancing, and
this one was the last-known working one"), and it is mighty annoying if
such a tag is used in describe output.
prev parent reply other threads:[~2008-03-17 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 0:41 git-describe only works on full tags Jan Engelhardt
2008-03-17 2:13 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vhcf6cd3e.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jengelh@computergmbh$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox