From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>, Elijah Newren <newren@gmail.com>
Subject: [PATCH 0/3] Backfill fixes and edges
Date: Wed, 15 Apr 2026 23:57:59 +0000 [thread overview]
Message-ID: <pull.2088.git.1776297482.gitgitgadget@gmail.com> (raw)
This topic fixes a few minor issues in git backfill (from ds/backfill-revs
this cycle), although some might see the third patch as more feature than
fix, and the first two patches are pretty minor and probably do not merit
consideration before the release this late in the cycle.
Overview:
* Patch 1: As a wise man once said, "Sending arbitrary command-line
arguments to setup_revisions() creates an opportunity for behavior you
are not expecting. For instance, can users...supply --first-parent? What
happens if they add an --author filter?" ;-) I think these particular
cases might work, but other rev-list options don't make sense, so let's
error on ones that don't.
* Patch 2: Making documentation more consistent with other commands
* Patch 3: Tweak the ranges so we actually prevent on-demand blob
downloading better with a new --[no-]include-edges flag.
Elijah Newren (3):
backfill: reject rev-list arguments that do not make sense
backfill: document acceptance of revision-range in more standard
manner
backfill: default to grabbing edge blobs too
Documentation/git-backfill.adoc | 22 ++++++-
builtin/backfill.c | 31 ++++++++-
t/t5620-backfill.sh | 110 ++++++++++++++++++++++++++++++--
3 files changed, 153 insertions(+), 10 deletions(-)
base-commit: 9f223ef1c026d91c7ac68cc0211bde255dda6199
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2088%2Fnewren%2Fbackfill-fixes-and-edges-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2088/newren/backfill-fixes-and-edges-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/2088
--
gitgitgadget
next 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 Elijah Newren via GitGitGadget [this message]
2026-04-15 23:58 ` [PATCH 1/3] backfill: reject rev-list arguments that do not make sense Elijah Newren via GitGitGadget
2026-04-16 14:11 ` 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=pull.2088.git.1776297482.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