From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>,
Elijah Newren <newren@gmail.com>,
Elijah Newren <newren@gmail.com>
Subject: [PATCH 1/3] backfill: reject rev-list arguments that do not make sense
Date: Wed, 15 Apr 2026 23:58:00 +0000 [thread overview]
Message-ID: <6c76f1e862790858297ff9b1debc1a38756b1913.1776297482.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2088.git.1776297482.gitgitgadget@gmail.com>
From: Elijah Newren <newren@gmail.com>
Some rev-list options accepted by setup_revisions() are silently
ignored or actively counterproductive when used with 'git backfill',
because the path-walk API has its own tree-walking logic that bypasses
the mechanisms these options rely on:
* -S/-G (pickaxe) and --diff-filter work by computing per-commit
diffs in get_revision_1() and filtering commits whose diffs don't
match. Since backfill's goal is to download all blobs reachable
from commits in the range, filtering out commits based on diff
content would silently skip blobs -- the opposite of what users
want.
* --follow disables path pruning (revs->prune) and only makes
sense for tracking a single file through renames in log output.
It has no useful interaction with backfill.
* -L (line-log) computes line-level diffs to track the evolution
of a function or line range. Like pickaxe, it filters commits
based on diff content, which would cause blobs to be silently
skipped.
* --diff-merges controls how merge commit diffs are displayed.
The path-walk API walks trees directly and never computes
per-commit diffs, so this option would be silently ignored.
* --filter (object filtering, e.g. --filter=blob:none) is used by
the list-objects traversal but is completely ignored by the
path-walk API, so it would silently do nothing.
Rather than letting users think these options are being honored,
reject them with a clear error message.
Signed-off-by: Elijah Newren <newren@gmail.com>
---
builtin/backfill.c | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/builtin/backfill.c b/builtin/backfill.c
index d794dd842f..a9edddcb7e 100644
--- a/builtin/backfill.c
+++ b/builtin/backfill.c
@@ -78,6 +78,28 @@ static int fill_missing_blobs(const char *path UNUSED,
return 0;
}
+static void reject_unsupported_rev_list_options(struct rev_info *revs)
+{
+ if (revs->diffopt.pickaxe)
+ die(_("'%s' cannot be used with 'git backfill'"),
+ (revs->diffopt.pickaxe_opts & DIFF_PICKAXE_REGEX) ? "-G" : "-S");
+ if (revs->diffopt.filter || revs->diffopt.filter_not)
+ die(_("'%s' cannot be used with 'git backfill'"),
+ "--diff-filter");
+ if (revs->diffopt.flags.follow_renames)
+ die(_("'%s' cannot be used with 'git backfill'"),
+ "--follow");
+ if (revs->line_level_traverse)
+ die(_("'%s' cannot be used with 'git backfill'"),
+ "-L");
+ if (revs->explicit_diff_merges)
+ die(_("'%s' cannot be used with 'git backfill'"),
+ "--diff-merges");
+ if (revs->filter.choice)
+ die(_("'%s' cannot be used with 'git backfill'"),
+ "--filter");
+}
+
static int do_backfill(struct backfill_context *ctx)
{
struct path_walk_info info = PATH_WALK_INFO_INIT;
@@ -144,6 +166,7 @@ int cmd_backfill(int argc, const char **argv, const char *prefix, struct reposit
if (argc > 1)
die(_("unrecognized argument: %s"), argv[1]);
+ reject_unsupported_rev_list_options(&ctx.revs);
repo_config(repo, git_default_config, NULL);
--
gitgitgadget
next prev parent reply other threads:[~2026-04-15 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 23:57 [PATCH 0/3] Backfill fixes and edges Elijah Newren via GitGitGadget
2026-04-15 23:58 ` Elijah Newren via GitGitGadget [this message]
2026-04-16 14:11 ` [PATCH 1/3] backfill: reject rev-list arguments that do not make sense Derrick Stolee
2026-04-15 23:58 ` [PATCH 2/3] backfill: document acceptance of revision-range in more standard manner Elijah Newren via GitGitGadget
2026-04-16 14:12 ` Derrick Stolee
2026-04-15 23:58 ` [PATCH 3/3] backfill: default to grabbing edge blobs too Elijah Newren via GitGitGadget
2026-04-16 14:15 ` Derrick Stolee
2026-04-16 14:18 ` [PATCH 0/3] Backfill fixes and edges Derrick Stolee
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=6c76f1e862790858297ff9b1debc1a38756b1913.1776297482.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@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