git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2025, #07; Fri, 24)
Date: Wed, 29 Jan 2025 08:40:34 -0500	[thread overview]
Message-ID: <8ddc3313-9d66-433e-847f-0330fd1d5e17@gmail.com> (raw)
In-Reply-To: <xmqqwmekvubv.fsf@gitster.g>

On 1/24/25 3:19 PM, Junio C Hamano wrote:


 > * ds/name-hash-tweaks (2024-12-20) 8 commits
 >   - pack-objects: add third name hash version
 >   - 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'?
 >   cf. <Z5E5KdbwHE7fmiJx@nand.local>
 >   source: <pull.1823.v3.git.1734715194.gitgitgadget@gmail.com>

After Taylor's review, I believe the latest version is ready
for 'next'.


> * 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
>   (this branch uses ds/path-walk-1.)
> 
>   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 plan to reroll this in a week or so. I wanted to focus on the
other series for a bit and will bring this back up (and may submit
the 'git-survey' series as well).

Thanks,
-Stolee


  parent reply	other threads:[~2025-01-29 13:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 20:19 What's cooking in git.git (Jan 2025, #07; Fri, 24) Junio C Hamano
2025-01-28 16:46 ` Jeff King
2025-01-28 17:59   ` Junio C Hamano
2025-01-28 18:26     ` Junio C Hamano
2025-01-29  6:03       ` Jeff King
2025-01-30  2:29       ` brian m. carlson
2025-01-30 17:26         ` Junio C Hamano
2025-01-29 13:40 ` Derrick Stolee [this message]
2025-01-29 15:03   ` 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=8ddc3313-9d66-433e-847f-0330fd1d5e17@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).