git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] doc: list filter-branch subdirectory-filter first

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 17, 2017, 02:46 UTC
Message-ID
<xmqqy3oapk3u.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<0102015f277a12fe-c69362e3-b14c-4b5c-abaa-4693fd6632c2-000000@eu-west-1.amazonses.com>
David Glasser <glasser@meteor.com> writes:
Show 7 quoted lines
> From: David Glasser <glasser@davidglasser.net>
>
> The docs claim that filters are applied in the listed order, so
> subdirectory-filter should come first.
> ---
>  Documentation/git-filter-branch.txt | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
Good.  Could you sign it off?

Somewhat related tangent is that we may want to also reorder the output from "git filter-branch -h" to the order of filter application. For that matter, the order in which the SYNOPSIS section lists these command line arguments may want to match, both for consistency and as an extra reminder to the users.

Previous: David GlasserNext: David Glasser
Message 2 of 4 in “doc: list filter-branch subdirectory-filter first”
  1. doc: list filter-branch subdirectory-filter firstDavid Glasser, Oct 16, 2017
  2. Junio C HamanoOct 17, 2017
  3. doc: list filter-branch subdirectory-filter firstDavid Glasser, Oct 17, 2017
  4. Junio C HamanoOct 18, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.