From: Jed Brown <jed@59A2.org>
To: Git List <git@vger.kernel.org>
Subject: git describe not showing "nearest" tag
Date: Sat, 04 May 2013 23:48:51 -0500 [thread overview]
Message-ID: <877gjeav64.fsf@mcs.anl.gov> (raw)
$ git rev-list --count v3.2..master
9651
$ git rev-list --count v3.3..master
6378
$ git describe --tags master
v3.2-9651-ga018267
I would have expected to see v3.3-6378-ga018267, given the documentation:
If multiple tags were found during the walk then the tag which has the
fewest commits different from the input committish will be selected
and output. Here fewest commits different is defined as the number of
commits which would be shown by git log tag..input will be the
smallest number of commits possible.
What's going on here?
The repository: https://bitbucket.org/petsc/petsc
This repository currently uses only lightweight tags. As an experiment,
I replaced both v3.2 and v3.3 with annotated tags, but it did not affect
the 'git describe' output.
next reply other threads:[~2013-05-05 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 4:48 Jed Brown [this message]
2013-05-05 6:42 ` git describe not showing "nearest" tag Junio C Hamano
2013-05-05 9:50 ` Jed Brown
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=877gjeav64.fsf@mcs.anl.gov \
--to=jed@59a2.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).