diff options
| author | Elijah Newren <newren@gmail.com> | 2026-04-15 23:58:01 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2026-04-15 20:32:21 -0700 |
| commit | ef6d3c94746462ec560893ed35c83df485a6344d (patch) | |
| tree | 3086bc3b306a0f55876fc7d550d33ea6401865d9 /git-remote-testgit | |
| parent | 6b79aee7de1ac7142707326699c3f4aa5b18cb28 (diff) | |
| download | git-ef6d3c94746462ec560893ed35c83df485a6344d.tar.gz git-ef6d3c94746462ec560893ed35c83df485a6344d.zip | |
backfill: document acceptance of revision-range in more standard manner
302aff09223f (backfill: accept revision arguments, 2026-03-26) added
support for passing revision arguments to 'git backfill' but documented
them only with a prose sentence:
You may also specify the commit limiting options from
git-rev-list(1).
No other command that accepts revision arguments documents them this
way. Commands like log, shortlog, and replay define a formal
<revision-range> entry and include rev-list-options.adoc. Commands like
bundle, fast-export, and filter-branch, which pass arguments through to
the revision machinery without including the full options file, still
define a formal <git-rev-list-args> entry explaining what is accepted.
Add a formal <revision-range> entry in the synopsis and OPTIONS section,
following the convention used by other commands, and mention that
commit-limiting options from git-rev-list(1) are also accepted.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-remote-testgit')
0 files changed, 0 insertions, 0 deletions