From: "Kristoffer Haugsbakk" <code@khaugsbakk•name>
To: rsbecker@nexbridge•com, "'Ben Boeckel'" <ben.boeckel@kitware•com>,
git@vger•kernel.org
Subject: Re: [BUG] `git describe` doesn't traverse the graph in topological order
Date: Fri, 22 Sep 2023 19:11:47 +0200 [thread overview]
Message-ID: <44a4e1e3-86d3-448a-ba6a-e78c63a6f85b@app.fastmail.com> (raw)
In-Reply-To: <02d701d9ed6f$abcb4b00$0361e100$@nexbridge.com>
On Fri, Sep 22, 2023, at 18:13, rsbecker@nexbridge•com wrote:
> On Friday, September 22, 2023 11:40 AM, Ben Boeckel wrote:
>>On Sat, Aug 12, 2023 at 15:36:56 -0400, Ben Boeckel wrote:
>>> I found an issue where `git describe` doesn't find a "closer" tag than
>>> another tag as the correct one to base the description off of. I have
>>> a reproducer, but I'll first give details of the real world issue.
>>
>>Bump. Can anyone provide guidance as to what the best solution to this might be?
>
> Can you provide details? `git describe` is sensitive to --first-parent
> and whether the tag has annotations.
> --Randall
Both of the tags (`v9.3.0.rc0` and `v9.3.0.rc1`) are annotated ones.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2023-09-22 17:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 19:36 [BUG] `git describe` doesn't traverse the graph in topological order Ben Boeckel
2023-09-22 15:39 ` Ben Boeckel
2023-09-22 16:13 ` rsbecker
2023-09-22 16:51 ` 'Ben Boeckel'
2023-09-22 17:14 ` rsbecker
2023-09-22 17:38 ` 'Ben Boeckel'
2023-09-22 17:51 ` Junio C Hamano
2023-09-22 18:12 ` rsbecker
2023-09-22 18:44 ` 'Ben Boeckel'
2023-09-22 18:49 ` rsbecker
2023-09-22 19:05 ` 'Ben Boeckel'
2023-09-22 19:27 ` rsbecker
2025-11-20 2:48 ` 'Ben Boeckel'
2025-11-20 8:05 ` Jeff King
2026-02-28 6:11 ` 'Ben Boeckel'
2023-09-22 18:41 ` 'Ben Boeckel'
2023-09-23 12:32 ` 'Ben Boeckel'
2023-09-22 17:11 ` Kristoffer Haugsbakk [this message]
2023-09-22 17:35 ` Kristoffer Haugsbakk
2023-09-22 17:43 ` 'Ben Boeckel'
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=44a4e1e3-86d3-448a-ba6a-e78c63a6f85b@app.fastmail.com \
--to=code@khaugsbakk$(echo .)name \
--cc=ben.boeckel@kitware$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=rsbecker@nexbridge$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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