All of lore.kernel.org
 help / color / mirror / Atom feed
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 (Jul 2023, #05; Tue, 25)
Date: Tue, 25 Jul 2023 18:39:25 -0400	[thread overview]
Message-ID: <ZMBPHTIacaWjy99D@nand.local> (raw)
In-Reply-To: <xmqqedkvk8u4.fsf@gitster.g>

On Tue, Jul 25, 2023 at 01:57:39PM -0700, Junio C Hamano wrote:
> * cc/repack-sift-filtered-objects-to-separate-pack (2023-07-24) 8 commits
>  - gc: add `gc.repackFilterTo` config option
>  - repack: implement `--filter-to` for storing filtered out objects
>  - gc: add `gc.repackFilter` config option
>  - repack: add `--filter=<filter-spec>` option
>  - repack: refactor finding pack prefix
>  - repack: refactor finishing pack-objects command
>  - t/helper: add 'find-pack' test-tool
>  - pack-objects: allow `--filter` without `--stdout`
>
>  "git repack" machinery learns to pay attention to the "--filter="
>  option.
>
>  Will merge to 'next'.
>  source: <20230724085909.3831831-1-christian.couder@gmail.com>

This may be a little soon to merge into 'next'. I looked at version 1
and had some concerns, but haven't had a chance to look at version 2.

Now that we have a third round, I'll take a look at it now. Sorry for
the hold up.

Thanks,
Taylor

  parent reply	other threads:[~2023-07-25 22:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 20:57 What's cooking in git.git (Jul 2023, #05; Tue, 25) Junio C Hamano
2023-07-25 20:59 ` Junio C Hamano
2023-07-25 21:17 ` Kousik Sanagavarapu
2023-07-25 21:50   ` Junio C Hamano
2023-07-26  2:41     ` Kousik Sanagavarapu
2023-07-25 22:39 ` Taylor Blau [this message]
2023-07-25 23:59   ` Junio C Hamano
2023-07-26 13:11 ` Phillip Wood
2023-07-26 16:34   ` Junio C Hamano
2023-07-27 21:24 ` Linus Arver
2023-07-27 21:52   ` 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=ZMBPHTIacaWjy99D@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 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.