From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2021, #04; Thu, 14)
Date: Fri, 15 Oct 2021 10:58:04 -0700 [thread overview]
Message-ID: <xmqq8ryu6uhf.fsf@gitster.g> (raw)
In-Reply-To: YWjfY3/62q6qNhFo@nand.local
Taylor Blau <me@ttaylorr.com> writes:
> On Thu, Oct 14, 2021 at 05:28:04PM -0700, Junio C Hamano wrote:
>> * tb/repack-write-midx (2021-10-07) 10 commits
>
> This reminded me to check on the status of
>
> https://lore.kernel.org/git/42a8d2ef-3a67-ca2c-4334-b79975d45da7@gmail.com/
>
> which hasn't been picked up yet. Stolee took a look and didn't have any
> problems, and I think this is an important one to pick up before you cut
> -rc0, since AFAICT `git multi-pack-index {expire,repack}` are broken on
> platforms that do not allow move-into-place when the destination is
> memory mapped.
Yeah, it is still on my rader. I think these four extra patches
build on tb/repack-write-midx, and I was waiting for the base topic
to stabilize (it had an "oops, this thing leaks" sent only a few
days before the add-on 4-patch series was sent, IIRC).
I think the base topic has been in 'next' for about a week, so it
probably is a good time to pick it up. Thanks for pinging.
next prev parent reply other threads:[~2021-10-15 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 0:28 What's cooking in git.git (Oct 2021, #04; Thu, 14) Junio C Hamano
2021-10-15 1:54 ` Taylor Blau
2021-10-15 9:48 ` Ævar Arnfjörð Bjarmason
2021-10-15 17:58 ` Junio C Hamano [this message]
2021-10-15 9:46 ` ab/test-cleanly-recreate-trash-directory Ævar Arnfjörð Bjarmason
2021-10-15 18:56 ` Submodules UX overhaul update (was: What's cooking in git.git (Oct 2021, #04; Thu, 14)) Emily Shaffer
2021-10-15 19:25 ` Submodules UX overhaul update Junio C Hamano
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=xmqq8ryu6uhf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).