From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, peff@peff.net
Subject: Re: What's cooking in git.git (Sep 2021, #05; Fri, 17)
Date: Fri, 17 Sep 2021 20:51:00 -0400 [thread overview]
Message-ID: <YUU39FVrAwwZbVqu@nand.local> (raw)
In-Reply-To: <xmqqlf3ug3q7.fsf@gitster.g>
On Fri, Sep 17, 2021 at 04:52:00PM -0700, Junio C Hamano wrote:
> * tb/repack-write-midx (2021-09-16) 8 commits
> [...]
> Will merge to 'next'?
I think this and the below topic are both ready to go, although...
> * tb/midx-write-propagate-namehash (2021-09-14) 7 commits
> [...]
> Will merge to 'next'?
...this one has received more attention than the other. And Peff said
that v3 of this series looked good to him [1].
So I think tb/midx-write-propagate-namehash would be ready to go. I
certainly stand by tb/repack-write-midx, but I would like a few others
to review it before merging it down.
Thanks,
Taylor
[1]: https://lore.kernel.org/git/YUUS4Mrh85KPucmi@coredump.intra.peff.net/
next prev parent reply other threads:[~2021-09-18 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 23:52 What's cooking in git.git (Sep 2021, #05; Fri, 17) Junio C Hamano
2021-09-18 0:51 ` Taylor Blau [this message]
2021-09-18 11:16 ` Carlo Arenas
2021-09-20 14:00 ` Derrick Stolee
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=YUU39FVrAwwZbVqu@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).