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 (May 2024, #08; Mon, 20)
Date: Tue, 21 May 2024 09:20:55 -0700 [thread overview]
Message-ID: <xmqqfrubb0go.fsf@gitster.g> (raw)
In-Reply-To: <Zkw5yDAVAnmy-cg8@tanuki> (Patrick Steinhardt's message of "Tue, 21 May 2024 08:06:00 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> On Mon, May 20, 2024 at 04:55:26PM -0700, Junio C Hamano wrote:
>> * ps/refs-without-the-repository-updates (2024-05-17) 17 commits
>> ...
>> Further clean-up the refs subsystem to stop relying on
>> the_repository, and instead use the repository associated to the
>> ref_store object.
>>
>> Will merge to 'next'?
>> source: <cover.1715929858.git.ps@pks.im>
>
> We've waited a couple more days now, and there was no additional
> feedback so far. I'm happy for this to be merged down.
>
>> * ps/reftable-reusable-iterator (2024-05-13) 13 commits
>> ...
>>
>> Code clean-up to make the reftable iterator closer to be reusable.
>>
>> Comments?
>> source: <cover.1715589670.git.ps@pks.im>
>
> There was a round of reviews by Justin on this one, which I've addressed
> in v2 and which was acked by him. I'll try to rope in more reviewers
> internally to get this over the finish line, but I'd also highly
> appreciate any GitLab-external reviews here.
Yeah, it was just me who didn't go back to the thread and update the
topic state. I think this one is in good enough shape to be merged
down.
>> * ps/reftable-write-options (2024-05-13) 11 commits
>> ...
>>
>> The knobs to tweak how reftable files are written have been made
>> available as configuration variables.
>>
>> Comments?
>> source: <cover.1715587849.git.ps@pks.im>
>
> Same here, I'll try to rope in additional reviewers.
Ditto.
FYI, the ones labeled as "Will merge to 'next'?" and "Comments?"
were often already read by me and I found nothing that needs further
comments by myself. The latter tends to be topics I am less sure
about (not about implementation, but assumptions and use cases the
topic is based on) than the former.
prev parent reply other threads:[~2024-05-21 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 23:55 What's cooking in git.git (May 2024, #08; Mon, 20) Junio C Hamano
2024-05-21 6:06 ` Patrick Steinhardt
2024-05-21 16:20 ` 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=xmqqfrubb0go.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.