Re: What's cooking in git.git (Feb 2024, #07; Tue, 20)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 21, 2024, 16:44 UTC
Message-ID: <xmqqle7drcm5.fsf@gitster.g>
In-Reply-To: <CAOLa=ZQOtDgyWxmV+C9r_wfqo-KdJ5uqW4KwJKD8WdT9qM0t2Q@mail.gmail.com>

Karthik Nayak <karthik.188@gmail.com> writes:

Show 17 quoted lines

>> * kn/for-all-refs (2024-02-12) 6 commits
>>  - for-each-ref: add new option to include root refs
>>  - ref-filter: rename 'FILTER_REFS_ALL' to 'FILTER_REFS_REGULAR'
>>  - refs: introduce `refs_for_each_include_root_refs()`
>>  - refs: extract out `loose_fill_ref_dir_regular_file()`
>>  - refs: introduce `is_pseudoref()` and `is_headref()`
>>  - Merge branch 'ps/reftable-backend' into kn/for-all-refs
>>  (this branch uses ps/reftable-backend.)
>>
>>  "git for-each-ref" filters its output with prefixes given from the
>>  command line, but it did not honor an empty string to mean "pass
>>  everything", which has been corrected.
>>
>>  Will merge to 'next'?
>>  source: <20240211183923.131278-1-karthik.188@gmail.com>
>
> Let me know if there's something more I could do here.

Hmph, I do not recall what the plan for this thing was. Wasn't it ejected from 'next' so that its UI can be rethought? Or did that happen already and what is in 'seen' already with a new UI?

Thanks.