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 (Mar 2022, #04; Thu, 17)
Date: Wed, 23 Mar 2022 11:27:14 -0700 [thread overview]
Message-ID: <xmqqo81wsewt.fsf@gitster.g> (raw)
In-Reply-To: <YjkloVk0BTqcgIiL@nand.local> (Taylor Blau's message of "Mon, 21 Mar 2022 21:25:53 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> On Thu, Mar 17, 2022 at 04:34:27AM -0700, Junio C Hamano wrote:
>> * tb/cruft-packs (2022-03-02) 17 commits
>>
>> A mechanism to pack unreachable objects into a "cruft pack",
>> instead of ejecting them into loose form to be reclaimed later, has
>> been introduced.
>>
>> Waiting for discussion to settle.
>> cf. <YiZI99yeijQe5Jaq@google.com>
>> source: <cover.1646266835.git.me@ttaylorr.com>
>
> I responded to Jonathan's message here:
>
> https://lore.kernel.org/git/YjkjaH61dMLHXr0d@nand.local/
>
> and I think it should be settled now. In an earlier thread, there was
> some discussion about whether or not a repository format extension is
> required. An extension is explicitly not required here, since the
> implementation of cruft packs was designed to avoid such a thing (see
> [1] for details on "why").
I think <Yjpxd8qhwnAIJJma@nand.local> yesterday is the last message
in that thread?
Let's see how well it goes.
Thanks.
next prev parent reply other threads:[~2022-03-23 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 11:34 What's cooking in git.git (Mar 2022, #04; Thu, 17) Junio C Hamano
2022-03-22 1:25 ` Taylor Blau
2022-03-23 18:27 ` Junio C Hamano [this message]
2022-03-23 19:20 ` Taylor Blau
2022-03-23 21:37 ` Junio C Hamano
2022-03-23 21:47 ` Taylor Blau
2022-03-22 16:05 ` gc/submodule-update-part2 (was Re: What's cooking in git.git (Mar 2022, #04; Thu, 17)) Glen Choo
2022-03-22 18:24 ` What's cooking in git.git (Mar 2022, #04; Thu, 17) Jeff Hostetler
2022-03-23 18:28 ` Junio C Hamano
2022-03-23 20:14 ` Jeff Hostetler
-- strict thread matches above, loose matches on Subject: below --
2022-03-19 18:08 Justin Donnelly
2022-03-21 16:51 ` 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=xmqqo81wsewt.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 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.