From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, derrickstolee@github.com, peff@peff.net
Subject: Re: [PATCH v2 0/3] midx: use `--stdin-packs` to implement `repack`
Date: Wed, 21 Sep 2022 12:09:31 -0700 [thread overview]
Message-ID: <xmqq35ck35p0.fsf@gitster.g> (raw)
In-Reply-To: <cover.1663706401.git.me@ttaylorr.com> (Taylor Blau's message of "Tue, 20 Sep 2022 16:40:14 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> Here's a few patches that replace the existing "feed each OID
> one-by-one" approach to implement the `repack` sub-command of the
> `multi-pack-index` builtin with one that uses `pack-objects`'s
> `--stdin-packs` option.
One question. How is this series expected to interact with the
7-patch series about ignoring cruft pack while "midx repack" etc.?
I guess it is not so urgent during the -rc period, so I'll stop at
asking that question without reading further, at least for now.
Thanks.
next prev parent reply other threads:[~2022-09-21 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YyokIf%2FSd7SYztKQ@nand.local>
2022-09-20 20:40 ` [PATCH v2 0/3] midx: use `--stdin-packs` to implement `repack` Taylor Blau
2022-09-20 20:40 ` [PATCH v2 1/3] midx.c: compute pack_info array outside of fill_included_packs_batch() Taylor Blau
2022-09-20 20:40 ` [PATCH v2 2/3] midx.c: use `pack-objects --stdin-packs` when repacking Taylor Blau
2022-09-23 18:23 ` Derrick Stolee
2022-09-23 18:28 ` Taylor Blau
2022-09-23 19:05 ` Derrick Stolee
2022-09-20 20:40 ` [PATCH v2 3/3] midx.c: unify `include_pack` array into `pack_info` struct Taylor Blau
2022-09-20 21:54 ` [PATCH v2 0/3] midx: use `--stdin-packs` to implement `repack` Jeff King
2022-09-21 19:09 ` Junio C Hamano [this message]
2022-09-23 18:29 ` Taylor Blau
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=xmqq35ck35p0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.