From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: What's cooking in git.git (Jun 2023, #01; Thu, 1)
Date: Thu, 1 Jun 2023 09:46:28 -0400 [thread overview]
Message-ID: <56359570-65f0-0916-310e-2d8a1d8e6b1f@github.com> (raw)
In-Reply-To: <xmqqedmva3wa.fsf@gitster.g>
On 6/1/2023 6:11 AM, Junio C Hamano wrote:
> * ds/disable-replace-refs (2023-06-01) 3 commits
> - repository: create read_replace_refs setting
> - replace-objects: create wrapper around setting
> - repository: create disable_replace_refs()
> (this branch uses tb/pack-bitmap-traversal-with-boundary.)
>
> Introduce a mechanism to disable replace refs globally and per
> repository.
>
> Will merge to 'next'???
> source: <pull.1537.git.1685126617.gitgitgadget@gmail.com>
Please wait at least for a v2. Patch 1 could use some cleanup, and
I have the changes staged locally while giving time for more review.
I'll get a v2 out by tomorrow.
> What's the doneness of the base topic?
I'm happy with Taylor's v3 of tb/pack-bitmap-traversal-with-boundary.
Thanks,
-Stolee
prev parent reply other threads:[~2023-06-01 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 10:11 What's cooking in git.git (Jun 2023, #01; Thu, 1) Junio C Hamano
2023-06-01 13:46 ` Derrick Stolee [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=56359570-65f0-0916-310e-2d8a1d8e6b1f@github.com \
--to=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).