git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #02; Wed, 3)
Date: Thu, 04 Sep 2025 09:23:15 -0700	[thread overview]
Message-ID: <xmqqy0qu9ogc.fsf@gitster.g> (raw)
In-Reply-To: <aLmhjw2xAbUogL1L@pks.im> (Patrick Steinhardt's message of "Thu, 4 Sep 2025 16:26:23 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> On Wed, Sep 03, 2025 at 10:07:49PM -0700, Junio C Hamano wrote:
>> * jt/de-global-bulk-checkin (2025-08-22) 4 commits
>>  - bulk-checkin: use repository variable from transaction
>>  - bulk-checkin: require transaction for index_blob_bulk_checkin()
>>  - bulk-checkin: remove global transaction state
>>  - bulk-checkin: introduce object database transaction structure
>> 
>>  The bulk-checkin code used to depend on a file-scope static
>>  singleton variable, which has been updated to pass an instance
>>  throughout the callchain.
>> 
>>  Will merge to 'next'?
>>  source: <20250822213500.1488064-1-jltobler@gmail.com>
>
> The series looks good to me, so I think it should be ready for prime
> time.

Yup, I am fairly familiar with the area, and I didn't see anything
questionable in the updates.  Let's move it forward.

Thanks.

      reply	other threads:[~2025-09-04 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04  5:07 What's cooking in git.git (Sep 2025, #02; Wed, 3) Junio C Hamano
2025-09-04  6:55 ` Kristoffer Haugsbakk
2025-09-04 16:21   ` Junio C Hamano
2025-09-05  0:21     ` Ben Knoble
2025-09-04 13:24 ` Lucas Seiki Oshiro
2025-09-04 16:21   ` Junio C Hamano
2025-09-04 14:26 ` Patrick Steinhardt
2025-09-04 16:23   ` 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=xmqqy0qu9ogc.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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).