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

Re: [PATCH 3/3] githooks.txt: Minor improvements to the grammar & phrasing

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Apr 26, 2016, 16:55 UTC
Message-ID
<CACBZZX4R99fJXoBjO_Ca7b+uAPf=7pH=gW8mq5Ae_BSA3v=G=g@mail.gmail.com>
In-Reply-To
<xmqqinz5les6.fsf@gitster.mtv.corp.google.com>
On Mon, Apr 25, 2016 at 8:33 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 7 quoted lines
> Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:
>
>> -This hook is invoked by 'git am' script.  It takes a single
>> +This hook is invoked by 'git am'.  It takes a single
>
> Good, as it does not matter to the readers that "am" happens to be
> implemented as a script.

Yeah, no need to mention it being a script. But aside from that I was mainly trying to fix grammar errors:

* Incorrect: "This is invoked by 'git am' script"
* Correct: "This is invoked by the 'git am' script"
* Correct: "This is invoked by a 'git am' script"
I.e. a few things in these docs were missing the definite/indefinite article.
Show 8 quoted lines
>>  parameter, the name of the file that holds the proposed commit
>> -log message.  Exiting with non-zero status causes
>> -'git am' to abort before applying the patch.
>> +log message.  Exiting with non-zero causes 'git am' to abort
>> +before applying the patch.
>
> I am not sure why you dropped "status" from here.  The result is
> harder to grok, at least to me.  Perhaps "with a non-zero status"?
I'm not 100% sure about this actually, but I thought:
* Incorrect: "Exiting with non-zero status"
* Correct: "Exiting with non-zero"
* Correct: "Exiting with a non-zero status".

I.e. the first one is missing an "a", I thought I'd just make it more brief, but sure, I'll make it "a non-zero status".

Show 10 quoted lines
>>  The hook is allowed to edit the message file in place, and can
>> -be used to normalize the message into some project standard
>> -format (if the project has one). It can also be used to refuse
>> -the commit after inspecting the message file.
>> +be used to e.g. normalize the message into some project standard
>> +format. It can also be used to refuse the commit after inspecting
>> +the message file.
>
> OK.  Or we can even drop "e.g." and the result still reads perfectly
> fine.
Done, and willdo too for the other occurrence.
Show 11 quoted lines
>>  This hook is invoked by 'git commit', and can be bypassed
>> -with `--no-verify` option.  It takes no parameter, and is
>> +with the `--no-verify` option.  It takes no parameters, and is
>>  invoked before obtaining the proposed commit log message and
>> -making a commit.  Exiting with non-zero status from this script
>> -causes the 'git commit' to abort.
>> +making a commit.  Exiting with a non-zero status from this script
>> +causes the 'git commit' command to abort before creating a commit.
>
> Good.  And you kept "status" here, which is doubly good.
>
Previous: Junio C HamanoNext: Eric Sunshine
Message 9 of 17 in “githooks.txt: Improve the intro section”
  1. 1/3 githooks.txt: Improve the intro sectionÆvar Arnfjörð Bjarmason, Apr 24, 2016
  2. 2/3 githooks.txt: Amend dangerous advice about 'update' hook ACLÆvar Arnfjörð Bjarmason, Apr 24, 2016
  3. Jacob KellerApr 24, 2016
  4. 2/3 githooks.txt: Amend dangerous advice about 'update' hook ACLÆvar Arnfjörð Bjarmason, Apr 24, 2016
  5. Junio C HamanoApr 25, 2016
  6. Ævar Arnfjörð BjarmasonApr 26, 2016
  7. 3/3 githooks.txt: Minor improvements to the grammar & phrasingÆvar Arnfjörð Bjarmason, Apr 24, 2016
  8. Junio C HamanoApr 25, 2016
  9. Ævar Arnfjörð BjarmasonApr 26, 2016
  10. Eric SunshineApr 25, 2016
  11. 0/3 Improvements to githooks.txt documentationÆvar Arnfjörð Bjarmason, Apr 25, 2016
  12. 1/3 githooks.txt: Improve the intro sectionÆvar Arnfjörð Bjarmason, Apr 25, 2016
  13. 2/3 githooks.txt: Amend dangerous advice about 'update' hook ACLÆvar Arnfjörð Bjarmason, Apr 25, 2016
  14. 3/3 githooks.txt: Minor improvements to the grammar & phrasingÆvar Arnfjörð Bjarmason, Apr 25, 2016
  15. Junio C HamanoApr 25, 2016
  16. Junio C HamanoApr 25, 2016
  17. Ævar Arnfjörð BjarmasonApr 26, 2016

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.