From: Derrick Stolee Date: Thu, 16 Apr 2026 14:12:14 GMT Subject: Re: [PATCH 2/3] backfill: document acceptance of revision-range in more standard manner Message-ID: <3c9df807-90b5-49c7-92b7-cb5cf6f4f0df@gmail.com> In-Reply-To: <173831ec92ea712a72f790f3a8eea6643ef7488b.1776297482.git.gitgitgadget@gmail.com> On 4/15/2026 7:58 PM, Elijah Newren via GitGitGadget wrote: > From: Elijah Newren > > 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 > 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 entry explaining what is accepted. > > Add a formal 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. Thanks for your attention to detail here. I like this version. -Stolee