git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>,
	shejialuo <shejialuo@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2025, #04; Tue, 14)
Date: Thu, 16 Jan 2025 11:24:01 +0100	[thread overview]
Message-ID: <Z4jeQSLmARruE5l3@pks.im> (raw)
In-Reply-To: <xmqqzfjt2qye.fsf@gitster.g>

On Tue, Jan 14, 2025 at 10:25:13AM -0800, Junio C Hamano wrote:
> * sj/ref-consistency-checks-more (2025-01-06) 10 commits
>  - builtin/fsck: add `git refs verify` child process
>  - packed-backend: check whether the "packed-refs" is sorted
>  - packed-backend: add check for object consistency
>  - packed-backend: create "fsck_packed_ref_entry" to store parsing info
>  - packed-backend: add "packed-refs" entry consistency check
>  - packed-backend: check whether the refname contains NULL binaries
>  - packed-backend: add "packed-refs" header consistency check
>  - packed-backend: check whether the "packed-refs" is regular
>  - builtin/refs.h: get worktrees without reading head info
>  - files-backend: add object check for regular ref
> 
>  "git fsck" becomes more careful when checking the refs.
>  source: <Z3qNUizvHJLgMx1y@ArchLinux>

I haven't yet found the time to have a look, but hope to do so tomorrow.

> * ds/backfill (2024-12-20) 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.
> 
>  Comments?
>  source: <pull.1820.v2.git.1734712193.gitgitgadget@gmail.com>

I had a couple of nits and expect another reroll, but think it's close
to being ready.

> * ds/path-walk-1 (2024-12-20) 7 commits
>  - path-walk: reorder object visits
>  - path-walk: mark trees and blobs as UNINTERESTING
>  - path-walk: visit tags and cached objects
>  - path-walk: allow consumer to specify object types
>  - t6601: add helper for testing path-walk API
>  - test-lib-functions: add test_cmp_sorted
>  - path-walk: introduce an object walk by path
>  (this branch is used by ds/backfill.)
> 
>  Introduce a new API to visit objects in batches based on a common
>  path, or by type.
> 
>  Comments?
>  source: <pull.1818.v4.git.1734711675.gitgitgadget@gmail.com>

I had a single nit, but don't necessarily think that it needs to be
addressed.

Patrick

  reply	other threads:[~2025-01-16 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 18:25 What's cooking in git.git (Jan 2025, #04; Tue, 14) Junio C Hamano
2025-01-16 10:24 ` Patrick Steinhardt [this message]
2025-01-16 16: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=Z4jeQSLmARruE5l3@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=shejialuo@gmail.com \
    --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).