From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #09; Mon, 22)
Date: Wed, 24 Sep 2025 12:01:51 -0700 [thread overview]
Message-ID: <xmqq8qi3llnk.fsf@gitster.g> (raw)
In-Reply-To: <aNOTMtVC0ArCSTRS@szeder.dev> ("SZEDER Gábor"'s message of "Wed, 24 Sep 2025 08:44:02 +0200")
SZEDER Gábor <szeder.dev@gmail.com> writes:
>> * jt/odb-transaction (2025-09-16) 7 commits
>> - odb: add transaction interface
>> - object-file: update naming from bulk-checkin
>> - object-file: relocate ODB transaction code
>> - bulk-checkin: drop flush_odb_transaction()
>> - builtin/update-index: end ODB transaction when --verbose is specified
>> - bulk-checkin: remove ODB transaction nesting
>> - Merge branch 'jt/de-global-bulk-checkin' into jt/odb-transaction
>>
>> Continue the work to build on the bulk-checkin infrastructure to
>> create many objects at once in a transaction and abstract it into
>> the generic object layer.
>>
>> Will merge to 'next'.
>> source: <20250916182938.2193476-1-jltobler@gmail.com>
>
> The merge of this topic into 'jch' modifies 'object-file.c' by
> replacing a call to reprepare_packed_git() with odb_reprepare(), but
> at that point the latter function doesn't exists yet, as it will only
> be introduced in 'ps/packfile-store', which is merged later.
Thanks. This is because there was a merge-fix defined for this
topic that was written back when this topic were less ready than the
other one. I'd need to move that merge-fix to the other topic to
correct it.
Thanks for catching while this topic was still outside 'next'.
prev parent reply other threads:[~2025-09-24 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 23:01 What's cooking in git.git (Sep 2025, #09; Mon, 22) Junio C Hamano
2025-09-23 3:19 ` Jeff King
2025-09-23 14:14 ` Junio C Hamano
2025-09-23 7:42 ` Patrick Steinhardt
2025-09-23 14:34 ` Junio C Hamano
2025-09-24 6:44 ` SZEDER Gábor
2025-09-24 7:00 ` Patrick Steinhardt
2025-09-24 19:01 ` 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=xmqq8qi3llnk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.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).