Re: [PATCH 0/5] backfill: accept revision arguments
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Mar 19, 2026, 09:54 UTC
- Message-ID
- <abvH29wYAFzk6V0F@pks.im>
- In-Reply-To
- <pull.2070.git.1773707361.gitgitgadget@gmail.com>
On Tue, Mar 17, 2026 at 12:29:16AM +0000, Derrick Stolee via GitGitGadget wrote:
Show 23 quoted lines
> The git backfill command assists in downloading missing blobs for blobless > partial clones. However, its current version lacks some valuable > functionality. It currently: > > 1. Only walks commits reachable from HEAD. > 2. It walks all reachable commits to the full history. > 3. It can focus on the current sparse-checkout definition, but otherwise it > doesn't focus on a given pathspec. > > All of these are being updated by this patch series, which allows rev-list > options to impact the path-walk. These include: > > 1. Specifying a given refspec, including --all. > 2. Modifying the commit walk, including --first-parent, commit ranges, or > recency using --since. > 3. Modifying the set of paths to download using pathspecs. > > One particularly valuable situation here is that now a user can run git > backfill -- <path> to download all versions of a specific file or a specific > directory, accelerating history queries within that path without downloading > more than necessary. This can accelerate git blame or git log -L for these > paths, where normally those commands download missing blobs one-by-one > during its diff algorithms.
Nice.
I think especially blaming is a bit of a sore spot -- downloading blobs one by one simply doesn't cut it there. I wonder whether we can easily use the backfill mechanism to fetch blobs automatically in git-blame(1) so that the user doesn't need to know about git-backfill(1) at all?
Patrick