From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ds/pack-name-hash-tweak (was Re: What's cooking in git.git (Oct 2024, #04; Sun, 6))
Date: Tue, 08 Oct 2024 13:45:34 -0700 [thread overview]
Message-ID: <xmqqfrp6z5ld.fsf@gitster.g> (raw)
In-Reply-To: <f89ba1ef-4cd4-4963-8de0-0323216246aa@gmail.com> (Derrick Stolee's message of "Tue, 8 Oct 2024 14:36:26 -0400")
Derrick Stolee <stolee@gmail.com> writes:
> This topic has been on hold waiting for greater interest in this
> approach. It was the first topic carved out of the path-walk API
> RFC due to how simple the change was, but the 'git pack-objects
> --path-walk' feature is a higher priority for helping Git clients
> and is now available for review [1].
>
> Junio: please pull ds/pack-name-hash-tweak out of 'seen'.
Will do. Thanks.
prev parent reply other threads:[~2024-10-08 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:53 What's cooking in git.git (Oct 2024, #04; Sun, 6) Junio C Hamano
2024-10-08 18:36 ` ds/pack-name-hash-tweak (was Re: What's cooking in git.git (Oct 2024, #04; Sun, 6)) Derrick Stolee
2024-10-08 20:45 ` Junio C Hamano [this message]
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=xmqqfrp6z5ld.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stolee@gmail.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).