From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: What's cooking in git.git (Sep 2024, #06; Mon, 16)
Date: Wed, 18 Sep 2024 13:33:57 -0700 [thread overview]
Message-ID: <xmqq7cb8bt1m.fsf@gitster.g> (raw)
In-Reply-To: <ZulUa3PL9zh6AqmR@pks.im> (Patrick Steinhardt's message of "Tue, 17 Sep 2024 12:05:31 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> On Mon, Sep 16, 2024 at 07:02:45PM -0700, Junio C Hamano wrote:
>> * ps/reftable-exclude (2024-09-16) 7 commits
>> - refs/reftable: wire up support for exclude patterns
>> - reftable/reader: make table iterator reseekable
>> - t/unit-tests: introduce reftable library
>> - Makefile: stop listing test library objects twice
>> - builtin/receive-pack: fix exclude patterns when announcing refs
>> - refs: properly apply exclude patterns to namespaced refs
>> - Merge branch 'cp/unit-test-reftable-stack' into ps/reftable-exclude
>> (this branch is used by ps/reftable-alloc-failures.)
>>
>> The reftable backend learned to more efficiently handle exclude
>> patterns while enumerating the refs.
>>
>> Will merge to 'next'?
>> source: <cover.1726476401.git.ps@pks.im>
>
> I was waiting for Taylor's review as he has written the original logic
> for the "files" backend. It came in this morning, and after some back
> and forth on the second version he agreed that the current version looks
> good, so this is ready to be merged from my point of view.
Thanks, both.
prev parent reply other threads:[~2024-09-18 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 2:02 What's cooking in git.git (Sep 2024, #06; Mon, 16) Junio C Hamano
2024-09-17 10:05 ` Patrick Steinhardt
2024-09-18 20:33 ` 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=xmqq7cb8bt1m.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--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