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

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 3, 2025, 17:57 UTC
Message-ID: <xmqqo6pjt2wn.fsf@gitster.g>
In-Reply-To: <aQRaRuBtt_r7SamL@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 15 quoted lines

>> * ps/ref-peeled-tags (2025-10-23) 16 commits
>>  - ref-filter: parse objects on demand
>> ...
>>  - Merge branch 'jt/repo-structure' into ps/ref-peeled-tags
>>  - Merge branch 'tb/incremental-midx-part-3.1' into ps/ref-peeled-tags
>>  (this branch is used by kn/refs-optim-cleanup; uses jt/repo-structure.)
>> 
>>  Some ref backend storage can hold not just the object name of an
>>  annotated tag, but the object name of the object the tag points at.
>>  The code to handle this information has been streamlined.
>> 
>>  Will merge to 'next' after base topics are merged.
>>  source: <20251023-b4-pks-ref-filter-skip-parsing-objects-v4-0-2be68ce82c9a@pks.im>
>
> Both dependencies have landed, so this should be ready to be merged now.

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.