From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #12; Thu, 30)
Date: Mon, 03 Nov 2025 10:43:12 -0800 [thread overview]
Message-ID: <xmqqh5vbt0sf.fsf@gitster.g> (raw)
In-Reply-To: <xmqqo6pjt2wn.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 03 Nov 2025 09:57:28 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> The tip of 'next' as of today after merging this topic, it seems.
>
> $ git tag --list --sort=version:tag 'v*.0'
>
> no longer works correctly and shows ascii sort.
>
> v1.0.0
> v1.1.0
> ...
> v2.0.0
> v2.1.0
> v2.10.0
> v2.11.0
> ...
> v2.19.0
> v2.2.0
> v2.20.0
> v2.21.0
> ...
> v2.49.0
> v2.5.0
> v2.50.0
> v2.51.0
> v2.6.0
> v2.7.0
> v2.8.0
> v2.9.0
>
> The merge on 'next' immediately before this topic got merged, i.e.,
> 9ab444ed (Merge branch 'tc/last-modified-active-paths-optimization'
> into next, 2025-11-03), is the last commit on the 'next'
> first-parent chain with which the above command works correctly.
>
> I haven't dug it further yet.
Bisect points at 054f5f45 (ref-filter: parse objects on demand,
2025-10-23), which is unfortunate, as that is the motivating step of
the whole topic.
next prev parent reply other threads:[~2025-11-03 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 21:36 What's cooking in git.git (Oct 2025, #12; Thu, 30) Junio C Hamano
2025-10-31 6:42 ` Patrick Steinhardt
2025-10-31 15:51 ` Junio C Hamano
2025-10-31 17:33 ` Eric Sunshine
2025-11-03 14:50 ` Lucas Seiki Oshiro
2025-11-03 17:57 ` Junio C Hamano
2025-11-03 18:43 ` Junio C Hamano [this message]
2025-11-03 20:10 ` Junio C Hamano
2025-11-03 21:30 ` Jeff King
2025-11-04 12:40 ` Patrick Steinhardt
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=xmqqh5vbt0sf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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).