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

Re: [PATCH 4/4] Documentation/git-commit.txt: correct a few minor grammatical mistakes

From
Brandon Casey <drafnel@gmail.com>
Date
Feb 19, 2013, 07:18 UTC
Message-ID
<CA+sFfMf8juf0rQh6S2sW=_LmsbhPc=c+erVppsZbAw-+h-4CqQ@mail.gmail.com>
In-Reply-To
<20130219064304.GG19757@elie.Belkin>
On Mon, Feb 18, 2013 at 10:43 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 20 quoted lines
> Brandon Casey wrote:
>
>> --- a/Documentation/git-commit.txt
>> +++ b/Documentation/git-commit.txt
>> @@ -174,10 +174,10 @@ OPTIONS
>>  --cleanup=<mode>::
>>       This option sets how the commit message is cleaned up.
>>       The  '<mode>' can be one of 'verbatim', 'whitespace', 'strip',
>> -     and 'default'. The 'default' mode will strip leading and
>> +     or 'default'. The 'default' mode will strip leading and
>>       trailing empty lines and #commentary from the commit message
>> -     only if the message is to be edited. Otherwise only whitespace
>> -     removed. The 'verbatim' mode does not change message at all,
>> +     only if the message is to be edited. Otherwise only whitespace is
>> +     removed. The 'verbatim' mode does not change the message at all,
>>       'whitespace' removes just leading/trailing whitespace lines
>>       and 'strip' removes both whitespace and commentary. The default
>>       can be changed by the 'commit.cleanup' configuration variable
>
> Yeah, the current text is a bit choppy.  How about this?

Hmm, I think the original text was more confusing than I realized. I think we should reorder the cleanup modes, placing "default" last, and then describe default in terms of either strip or whitespace depending on whether an editor will be spawned.

Show 33 quoted lines
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
>
> --- i/Documentation/git-commit.txt
> +++ w/Documentation/git-commit.txt
> @@ -172,16 +172,25 @@ OPTIONS
>         linkgit:git-commit-tree[1].
>
>  --cleanup=<mode>::
> -       This option sets how the commit message is cleaned up.
> -       The  '<mode>' can be one of 'verbatim', 'whitespace', 'strip',
> -       and 'default'. The 'default' mode will strip leading and
> -       trailing empty lines and #commentary from the commit message
> -       only if the message is to be edited. Otherwise only whitespace
> -       removed. The 'verbatim' mode does not change message at all,
> -       'whitespace' removes just leading/trailing whitespace lines
> -       and 'strip' removes both whitespace and commentary. The default
> -       can be changed by the 'commit.cleanup' configuration variable
> -       (see linkgit:git-config[1]).
> +       This option determines how the supplied commit message should be
> +       cleaned up before committing. The '<mode>' can be `verbatim`,
> +       `whitespace`, `strip`, or `default`.
> ++
> +--
> +default::
> +       Strip leading and trailing empty lines and #commentary from
> +       the commit message only if the message is to be edited.
> +       Otherwise only remove whitespace.
> +verbatim::
> +       Do not change the message at all.
> +whitespace::
> +       Remove only leading and trailing whitespace lines.
> +strip::
> +       Remove both whitespace and commentary.
Let's reorder these.  Maybe something like this:
+strip::
+       Strip leading and trailing empty lines, trailing whitespace
and #commentary and
+       collapse consecutive blank lines into one.
+whitespace::
+       Same as "strip" except #commentary is not removed.
+verbatim::
+       Do not change the message at all.
+default::
+       "strip" if the message is to be edited.  Otherwise "whitespace".
Show 7 quoted lines
> +--
> ++
> +The default can be changed using the 'commit.cleanup' configuration
> +variable (see linkgit:git-config[1]).
>
>  -e::
>  --edit::
-Brandon
Previous: Jonathan NiederNext: Jonathan Nieder
Message 8 of 19 in “t/t7502: compare entire commit message with what was expected”
  1. 1/4 t/t7502: compare entire commit message with what was expectedBrandon Casey, Feb 19, 2013
  2. 2/4 t7502: demonstrate breakage with a commit message with trailing newlinesBrandon Casey, Feb 19, 2013
  3. Jonathan NiederFeb 19, 2013
  4. 3/4 git-commit: only append a newline to -m mesg if necessaryBrandon Casey, Feb 19, 2013
  5. Jonathan NiederFeb 19, 2013
  6. 4/4 Documentation/git-commit.txt: correct a few minor grammatical mistakesBrandon Casey, Feb 19, 2013
  7. Jonathan NiederFeb 19, 2013
  8. Brandon CaseyFeb 19, 2013
  9. Jonathan NiederFeb 19, 2013
  10. Junio C HamanoFeb 19, 2013
  11. 4/4 Documentation/git-commit.txt: rework the --cleanup sectionBrandon Casey, Feb 19, 2013
  12. 4/4 Documentation/git-commit.txt: rework the --cleanup sectionBrandon Casey, Feb 19, 2013
  13. 4/4 Documentation/git-commit.txt: rework the --cleanup sectionBrandon Casey, Feb 19, 2013
  14. fixup! Documentation/git-commit.txt: rework the --cleanup sectionJonathan Nieder, Feb 19, 2013
  15. Brandon CaseyFeb 19, 2013
  16. Junio C HamanoFeb 19, 2013
  17. Jonathan NiederFeb 19, 2013
  18. Jonathan NiederFeb 19, 2013
  19. Junio C HamanoFeb 19, 2013

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.