Re: What's cooking in git.git (Sep 2026, #04)

[Junio C Hamano <gitster@pobox.com>]

Patrick Steinhardt <ps@pks.im> writes:

> On Thu, Sep 10, 2026 at 10:39:02AM -0700, Junio C Hamano wrote:
>> * bc/maintenance-doc-markup-fix-for-asciidoc (2026-09-09) 1 commit
>>  - doc: fix conjoined maintenance strategies in git-config(1)
>> 
>>  Mark-up fix for 'git maintenance' documentation pages.
>> 
>>  Will merge to 'next'?
>>  cf. <aqJntwrjC4ImuSyW@pks.im>
>>  source: <20260910-maintenance-doc-bullet-fix-v2-1-3ed1c75e24b2@brighamcampbell.com>
>
> Yup, this version looks good to me.

Yup.  We are after the -rc0 preview so let me fast track 'next'
candidates, which usually spends one week in 'next' before moving to
'master', earlier than usual.  A trivially-verifyable documentation
fix like this one is a best example.

>> * ps/libgit-in-subdir (2026-07-12) 2 commits
>>  . Move libgit.a sources into separate "lib/" directory
>>  . t/helper: prepare "test-example-tap.c" for introduction of "lib/"
>>  . Merge branch 'ps/odb-source-packed' into ps/libgit-in-subdir
>> 
>>  The source files for 'libgit.a' have been moved into a new 'lib/'
>>  directory to clean up the top-level directory and clearly separate
>>  library code.  This topic has been ejected for now, as it causes too
>>  many evil merges with other topics.
>> ...
> I didn't really have the feeling that I was gaining consensus on this
> series. Maybe I'll be able to build consensus at the Contributor's
> Summit, but until then we can probably just discard this series.

To be fair, I do not think anybody would unwelcome a change that
makes the sources easier to navigate---otherwise we wouldn't have
odb/ or even builtin/ hierarchies today.  It is just that different
people views how easier to navigate a concrete change proposed makes
the sources.

>> * ps/odb-stop-registering-in-memory-sources (2026-09-02) 13 commits
>>  ...
>>  Expecting a (hopefully small and final) reroll?
>>  cf. <aqD0F795VKJ6jUFd@pks.im>
>>  source: <20260902-pks-odb-registering-in-memory-sources-v2-0-c6ca12fdea4d@pks.im>
>
> I didn't plan to as it was only changing a single word in a commit
> message, but fair enough. Sent out v3 now.

Thanks, let's merge it down to 'next' now.