From: Jan Hudec <bulb@ucw.cz>
To: git@vger.kernel.org
Subject: [BUG] git describe number of commits different from git log count
Date: Fri, 05 Feb 2016 12:17:25 +0100 [thread overview]
Message-ID: <1701823.75Syo8h0k0@box> (raw)
Hello,
I have a repository with following situation:
$ git describe next
v4.1-2196-g5a414d7
$ git describe next --match=v4.2
v4.2-4757-g5a414d7
Since the tag with fewest commits since is selected, it appears logical.
However, v4.2 is descendant of v4.1, so it does not make sense for it to have
more commits since. And rev-list or log confirm that:
$ git rev-list v4.1..next | wc -l
2196
$ git rev-list v4.2..next | wc -l
1152
The number of commits since v4.1 matches what the describe counted, but the
number of commits since v4.2 does not.
The v4.1 tag should be reachable along the first parent path, the v4.2
definitely isn't, but I am not asking for first parent path.
I am using
$ git --version
git version 2.7.0
from Debian git 1:2.7.0-1 package locally, but our build server is still using
rather ancient
$ git --version
git version 1.8.4.msysgit.0
with exactly the same result.
Unfortunately I can't share the repository, but I could run some tests on it,
including rebuilding git with some diagnostics and trying that.
Note that the tag v4.2 is otherwise perfectly good candidate for describe and
gets used just fine when describing master:
$ git describe master
v4.2-2-g34eb80b
$ git describe master --match=v4.1
v4.1-1046-g34eb80b
However when I merged master into next, it started producing those incorrect
results.
--
- Jan Hudec <bulb@ucw.cz>
next reply other threads:[~2016-02-05 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 11:17 Jan Hudec [this message]
2016-12-05 23:27 ` git describe number of commits different from git log count Aaron Schrab
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1701823.75Syo8h0k0@box \
--to=bulb@ucw.cz \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).