From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org, me@ttaylorr.com, ps@pks.im
Subject: Re: What's cooking in git.git (Jan 2025, #09; Fri, 31)
Date: Mon, 03 Feb 2025 13:38:04 -0800 [thread overview]
Message-ID: <xmqqjza61zgj.fsf@gitster.g> (raw)
In-Reply-To: <d8661675-1c08-4c7c-9198-be7eabf0ebee@gmail.com> (Derrick Stolee's message of "Mon, 3 Feb 2025 12:10:21 -0500")
Derrick Stolee <stolee@gmail.com> writes:
> On 1/31/25 9:51 PM, Junio C Hamano wrote:
>
>> * ds/backfill (2025-01-23) 6 commits
>> - backfill: assume --sparse when sparse-checkout is enabled
>> - backfill: add --sparse option
>> - backfill: add --min-batch-size=<n> option
>> - backfill: basic functionality and tests
>> - backfill: add builtin boilerplate
>> - Merge branch 'ds/path-walk-1' into ds/backfill
>> Lazy-loading missing files in a blobless clone on demand is costly
>> as it tends to be one-blob-at-a-time. "git backfill" is introduced
>> to help bulk-download necessary files beforehand.
>> Expecting a reroll.
>> cf. <Z4jeQSLmARruE5l3@pks.im>
>> source: <pull.1820.v2.git.1734712193.gitgitgadget@gmail.com>
>
> I've updated this onto 'master' now that ds/path-walk-1 is merged. v3
> is imminent.
>
> It required a few updates that I'm sure you've been making within the
> merge in order to keep 'seen' building.
;-)
>> * ds/name-hash-tweaks (2025-01-27) 7 commits
>> - pack-objects: prevent name hash version change
>> - test-tool: add helper for name-hash values
>> - p5313: add size comparison test
>> - pack-objects: add GIT_TEST_NAME_HASH_VERSION
>> - repack: add --name-hash-version option
>> - pack-objects: add --name-hash-version option
>> - pack-objects: create new name-hash function version
>> "git pack-objects" and its wrapper "git repack" learned an option
>> to use an alternative path-hash function to improve delta-base
>> selection to produce a packfile with deeper history than window
>> size.
>> Will merge to 'next'?
>> source: <pull.1823.v4.git.1738004554.gitgitgadget@gmail.com>
> Since this is still marked with a question mark, I'll mention that
> the last version seems stable and has Taylor's review.
Indeed this has an Ack in <Z51DHdS8SStRGalX@nand.local>. Let's
merge it down to 'next'.
next prev parent reply other threads:[~2025-02-03 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 2:51 What's cooking in git.git (Jan 2025, #09; Fri, 31) Junio C Hamano
2025-02-03 17:10 ` Derrick Stolee
2025-02-03 21:38 ` Junio C Hamano [this message]
2025-02-04 10:07 ` Karthik Nayak
2025-02-04 17:48 ` 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=xmqqjza61zgj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
--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).