Re: What's cooking in git.git (Oct 2025, #12; Thu, 30)

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 3, 2025, 18:43 UTC
Message-ID: <xmqqh5vbt0sf.fsf@gitster.g>
In-Reply-To: <xmqqo6pjt2wn.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 34 quoted lines

> 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.