Re: What's cooking in git.git (Oct 2026, #10)

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

Patrick Steinhardt <ps@pks.im> writes:

>> * oa/bundle-uri-drop-the-repository (2026-10-28) 1 commit
>...
>>  source: <20261028093455.76247-1-okhuomonajayi54@gmail.com>
>
> The patch itself looks good, but I left a comment there that we can
> trivially get rid of the remaining two uses of `the_repository`, as
> well. And if so we could drop `USE_THE_REPOSITORY_VARIABLE` altogether.

Yup, I saw the updated one, and I agree it is sensible to go fill
the last tiny gap.

>> * sp/t0001-avoid-pipe (2026-10-22) 1 commit
>>  - t0001: avoid pipes in test scripts
>...
> Mostly there, but there's a formatting error in the commit message. You
> could fix that up manually, but seeing that this is in the context of
> Outreachy I think it's better to let the contributor fix this. Also
> because this issue was present in v2 already.

Yes.  I think v4 got rid of the empty line in the middle of the
sentence.

>> * sj/oss-fuzz-commit-graph-gitdir (2026-10-24) 1 commit
>>  - oss-fuzz: set a gitdir in the commit-graph fuzzer
>...
> I had a look, looks good to me.

Thanks.

>> * ps/odb-object-storage-extension (2026-10-26) 7 commits
> ...
> The only change I've got queued is this one:
>
> 2:  81f6d2b09e3 ! 2:  0f85938a5d2 setup: introduce object storage extension
>     @@ Commit message
>              allows you to configure a different location for the ".git/objects"
>              directory.
>      
>     -    Making the location of the "files" backend configurable is not he most
>     +    Making the location of the "files" backend configurable is not the most
>          thrilling feature of this new extension. But it gives us a couple of
>          advantages:
>
> I can send out a new version to fix this, but maybe this is something
> you could fix up locally? Whatever works best for you.

Amended locally.  Thanks.

>> * ps/gitlab-ci-whitespace-job-shallow-clone-fix (2026-10-16) 1 commit
>>  - gitlab-ci: fix "check" jobs with large merge requests
>> ...
>>  Needs review.
>>  cf. <CAOLa=ZTwyGnWFa4U=8UDzEUuyhQ7jT555FCh-CBp_wos9rJG9w@mail.gmail.com>
>>  source: <20261016-pks-ci-optional-whitespace-job-v1-1-f5693fbae1a5@pks.im>
>
> Karthik approved this, CI is happy and the fix is somewhat trivial. I'd
> hope that we can merge this soon-ish to fix our CI.

Yeah, the CAOLa= message is indeed the one that is happy with this
change.  Will mark for 'next'.

>> * kn/fetch-tag-backfill-batch-fix (2026-10-28) 3 commits
>> ...
> I expect another tiny reroll, but that should probably be the last one.

Replaced with the updated one, and noted your <auNReY6zQ5x7tlbV@pks.im>.

>> * ps/repo-ref-storage-format-fix (2026-10-05) 1 commit
>...
> I've got two positive reviews, so maybe this is ready to go?
>
> cf. <CAOLa=ZTNNY_XuixqZ96TK0zFfDpWvxSupxVGOnH1VGXK4KF_0w@mail.gmail.com>
> cf. <as61Dh7ui54gdzGV@denethor>

Indeed.

>> * mc/refs-rename-transaction (2026-10-08) 4 commits
>> ...
> I think this topic should be evicted for now. I don't think that the
> result is sensible, and it was way too AI-heavy without the author
> having a clear understanding of what they are doing.

OK, let's.