From: Kevin Daudt <me@ikke.info>
To: Istvan Pato <istvan.pato@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug in 'git describe' if I have two tags on the same commit.
Date: Mon, 13 Feb 2017 16:44:07 +0100 [thread overview]
Message-ID: <20170213154407.GA31568@alpha.ikke.info> (raw)
In-Reply-To: <CAOcUJQwnCJOhUUU2RqJP2H5YxUr4qCEpyDj_XiiQSe4V6rcBmg@mail.gmail.com>
On Sun, Feb 12, 2017 at 01:15:22PM +0100, Istvan Pato wrote:
> I didn't get back the latest tag by 'git describe --tags --always' if
> I have two tags on the same commit.
>
> // repository ppa:git-core/ppa
>
> (master)⚡ % cat /etc/lsb-release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=16.04
> DISTRIB_CODENAME=xenial
> DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
>
> (master)⚡ % git --version
> git version 2.11.0
>
> (master) [1] % git show-ref --tag
> 76c634390... refs/tags/1.0.0
> b77c7cd17... refs/tags/1.1.0
> b77c7cd17... refs/tags/1.2.0
>
> (master) % git describe --tags --always
> 1.1.0-1-ge9e9ced
>
> ### Expected: 1.2.0
>
> References:
>
> https://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.1.1.txt
>
> * "git describe" did not tie-break tags that point at the same commit
> correctly; newer ones are preferred by paying attention to the
> tagger date now.
>
> http://stackoverflow.com/questions/8089002/git-describe-with-two-tags-on-the-same-commit
>
> Thanks,
> Istvan Pato
Are these lightweight tags? Only annotated tags have a date associated
to them, which is where the rel-notes refers to.
next prev parent reply other threads:[~2017-02-13 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 12:15 Bug in 'git describe' if I have two tags on the same commit Istvan Pato
2017-02-13 15:44 ` Kevin Daudt [this message]
2017-02-13 20:35 ` Junio C Hamano
2017-02-14 8:07 ` Istvan Pato
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=20170213154407.GA31568@alpha.ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=istvan.pato@gmail.com \
/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