From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/pack-name-hash-tweak (was Re: What's cooking in git.git (Oct 2024, #04; Sun, 6))
Date: Tue, 8 Oct 2024 14:36:26 -0400 [thread overview]
Message-ID: <f89ba1ef-4cd4-4963-8de0-0323216246aa@gmail.com> (raw)
In-Reply-To: <xmqq4j5naozf.fsf@gitster.g>
On 10/7/24 11:53 AM, Junio C Hamano wrote:
> * ds/pack-name-hash-tweak (2024-10-04) 6 commits
> - test-tool: add helper for name-hash values
> - p5313: add size comparison test
> - git-repack: update usage to match docs
> - pack-objects: add GIT_TEST_FULL_NAME_HASH
> - repack: test --full-name-hash option
> - pack-objects: add --full-name-hash option
>
> In a repository with too many (more than --window size) similarly
> named files, "git repack" would not find good delta-base candidate
> and worse, it may not use a blob from exactly the same path as a
> good delta-base candidate. Optionally replace the name hash so
> that only blobs at the same path and nothing else are used as
> delta-base candidate.
>
> On hold.
> cf. <34346998-deac-4e1f-9d5f-218f664e9e08@gmail.com>
> source: <pull.1785.v2.git.1726692381.gitgitgadget@gmail.com>
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'.
[1] https://lore.kernel.org/git/pull.1813.git.1728396723.gitgitgadget@gmail.com
Thanks,
-Stolee
next prev parent reply other threads:[~2024-10-08 18:36 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 ` Derrick Stolee [this message]
2024-10-08 20:45 ` ds/pack-name-hash-tweak (was Re: What's cooking in git.git (Oct 2024, #04; Sun, 6)) 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=f89ba1ef-4cd4-4963-8de0-0323216246aa@gmail.com \
--to=stolee@gmail.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).