Git development
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Kevin Ballard <kevin@sb.org>
Cc: git list <git@vger.kernel.org>
Subject: Re: Git describe finding wrong tag
Date: Tue, 08 Feb 2011 08:19:36 +0100	[thread overview]
Message-ID: <4D50EE88.8070005@viscovery.net> (raw)
In-Reply-To: <A76F5A9B-6E22-40D5-A8C9-C471A22DF1BE@sb.org>

Am 2/8/2011 5:46, schrieb Kevin Ballard:
> I just encountered an odd situation where `git describe` insists on finding the
> wrong tag. In my case, I tagged a branch, then merged it into another branch,
> and now `git describe` in that other branch decides that it should emit a tag
> name that's over 200 commits old rather than the one that's a single commit
> away.
> 
> % git --version
> git version 1.7.4.31.g3f8c4
> % git describe
> build_1.2.2_applestore_1-203-g742967b
> % git describe HEAD^2
> build_1.2.2
> 
> Is there any rational for why git-describe is opting for the much older
> commit?

Most likely, the situation outlined in this commit message applies to your
case:

http://git.kernel.org/?p=git/git.git;a=commit;h=80dbae03

Then what you observe is by design.

-- Hannes

  reply	other threads:[~2011-02-08  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08  4:46 Git describe finding wrong tag Kevin Ballard
2011-02-08  7:19 ` Johannes Sixt [this message]
2011-02-08  7:23   ` Kevin Ballard

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=4D50EE88.8070005@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=kevin@sb.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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