From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Benjamin Kircher <bkircher@0xadd.de>, git@vger.kernel.org
Subject: Re: git log with %(describe) placeholder does not find most recent tag
Date: Mon, 11 Oct 2021 15:23:19 +0700 [thread overview]
Message-ID: <732e64ad-0ca0-d384-a09b-55c74479e254@gmail.com> (raw)
In-Reply-To: <61d28b8e9dd906eba821ecc9ee81bd4ac2374494.camel@0xadd.de>
On 11/10/21 15.08, Benjamin Kircher wrote:
> What did you do before the bug happened? (Steps to reproduce your
> issue)
>
> git log --format='%(describe)' -n1
>
> produces a different result than
>
> git describe --tags
>
> What did you expect to happen? (Expected behavior)
>
> I expected both to produce (roughly) the same result. At least,
> reference the same tag.
>
> What happened instead? (Actual behavior)
>
> git log --format='%(describe)' -n1
> v0.11.0
>
> and
>
> git log --format='%(describe)' -n1
> v0.3.0-beta-253-g4ccd023
>
> What's different between what you expected and what actually happened?
>
> git log with %(describe) placeholder does not seem to find the most
> recent tag as git-describe would do. Is this intended?
I tried to reproduce your issue. I have linux.git shallow repo (master
branch pulls from torvalds' mainline tree and stable branches pull from
stable tree). HEAD currently points to v5.15-rc5 tag.
The result (note that I use custom-compiled Git):
```
$ /opt/git/bin/git version
git version 2.33.0
$ /opt/git/bin/git log -n 1 --format='%(describe)'
v5.15-rc5
$ /opt/git/bin/git describe --tags
v5.15-rc5
```
Both results (git log and git describe) are same.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-10-11 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 8:08 git log with %(describe) placeholder does not find most recent tag Benjamin Kircher
2021-10-11 8:23 ` Bagas Sanjaya [this message]
2021-10-11 8:29 ` Benjamin Kircher
2021-10-11 12:27 ` Carlo Arenas
2021-10-11 16:23 ` Jeff King
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=732e64ad-0ca0-d384-a09b-55c74479e254@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bkircher@0xadd.de \
--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).