From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2025, #07; Sun, 23)
Date: Tue, 25 Nov 2025 09:19:03 -0800 [thread overview]
Message-ID: <xmqqpl96rpx4.fsf@gitster.g> (raw)
In-Reply-To: <87ldju5oim.fsf@iotcl.com> (Toon Claes's message of "Tue, 25 Nov 2025 12:40:17 +0100")
Toon Claes <toon@iotcl.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> * ps/object-source-management (2025-11-18) 14 commits
>> - odb: handle recreation of quarantine directories
>> - odb: handle changing a repository's commondir
>> - chdir-notify: add function to unregister listeners
>> - odb: handle initialization of sources in `odb_new()`
>> - http-push: stop setting up `the_repository` for each reference
>> - t/helper: stop setting up `the_repository` repeatedly
>> - builtin/index-pack: fix deferred fsck outside repos
>> - oidset: introduce `oidset_equal()`
>> - odb: move logic to disable ref updates into repo
>> - odb: refactor `odb_clear()` to `odb_free()`
>> - odb: adopt logic to close object databases
>> - setup: convert `set_git_dir()` to have file scope
>> - path: move `enter_repo()` into "setup.c"
>> - Merge branch 'ps/object-source-loose' into ps/object-source-management
>> (this branch uses ps/object-source-loose.)
>>
>> Code refactoring around object database sources.
>>
>> Comments?
>> source: <20251119-b4-pks-odb-creation-v1-0-2b2ed2612cb6@pks.im>
>
> I've read through the patches, and I've got no comments to add.
Thanks.
prev parent reply other threads:[~2025-11-25 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 4:59 What's cooking in git.git (Nov 2025, #07; Sun, 23) Junio C Hamano
2025-11-24 15:46 ` D. Ben Knoble
2025-11-24 18:26 ` Junio C Hamano
2025-12-22 22:06 ` D. Ben Knoble
2025-11-25 6:55 ` Elijah Newren
2025-11-25 17:18 ` Junio C Hamano
2025-11-25 11:40 ` Toon Claes
2025-11-25 17:19 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpl96rpx4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=toon@iotcl.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).