From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #03; Fri, 15)
Date: Fri, 15 Jan 2021 22:25:55 -0500 [thread overview]
Message-ID: <YAJcwzd7HjkwAOv1@nand.local> (raw)
In-Reply-To: <xmqqbldpr90k.fsf@gitster.c.googlers.com>
On Fri, Jan 15, 2021 at 05:00:11PM -0800, Junio C Hamano wrote:
> * tb/pack-revindex-on-disk (2021-01-14) 8 commits
> (this branch uses tb/pack-revindex-api.)
>
> Introduce an on-disk file to record revindex for packdata, which
> traditionally was always created on the fly and only in-core.
Thanks for dealing with some of the shuffle between this and the
tb/pack-revindex-api branch. I have a string of topics in my fork
that are based on this multi-series of patches, but I'll send them to
the list one at a time to avoid crossing topics.
I figured that sending these two at the same time would be worthwhile,
but seeing the pain it caused was enough to not make me want to send two
dependent topics at the same time again.
(There may some semi-related fixes--especially around .keep packs--that
I could pull out of the chain entirely, and so they could be submitted
alongside other topics without one depending on the other. I look into
whether or not it's possible next week.)
Thanks,
Taylor
next prev parent reply other threads:[~2021-01-16 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 1:00 What's cooking in git.git (Jan 2021, #03; Fri, 15) Junio C Hamano
2021-01-16 3:25 ` Taylor Blau [this message]
2021-01-16 5:32 ` Junio C Hamano
2021-01-16 4:21 ` Jiang Xin
2021-01-16 5:43 ` 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=YAJcwzd7HjkwAOv1@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).