Re: [PATCH v3 3/6] Change 'git' to 'Git' whenever the whole system is referred to #2
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 23, 2013, 04:17 UTC
- Message-ID
- <7v38xsjzxg.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CAJDDKr4fnUp_35ni72XJS_NSp4jxbvQPENLnk3AhFv2FBg3DTg@mail.gmail.com>
David Aguilar <davvid@gmail.com> writes:
Show 13 quoted lines
> On Mon, Jan 21, 2013 at 11:19 AM, Thomas Ackermann <th.acker@arcor.de> wrote: >> diff --git a/Documentation/config.txt b/Documentation/config.txt >> index b87f744..5a831ad2 100644 >> --- a/Documentation/config.txt >> +++ b/Documentation/config.txt >> push.default:: >> - Defines the action git push should take if no refspec is given >> + Defines the action Git push should take if no refspec is given >> on the command line, no refspec is configured in the remote, and >> no refspec is implied by any of the options given on the command >> line. Possible values are: > > This should probably be "git push" in double quotes.
Yeah, or no quotes, or `git push` even.
I've pushed the result of my nitpicks I sent so far as part of the 'pu' branch, on topic 'ta/doc-no-small-caps'. Its tip is now at bfb8e1e (fixup! Change 'git' to 'Git' whenever the whole system is referred to #4, 2013-01-22).
Thomas, I do not want to see many rounds of entire rerolls of this series on the list (nobody will look at the whole series multiple times with fine toothed comb). I do not think you want to do that either. Can you collect remaining fixups like David's message, turn them into patch form when you have collected enough to be reviewed in one sitting (say, a patchfile at around 200 lines), and send them over to the list to apply on top of the tree of that commit?
After a week or so, I'll squash the series into two commits (the first one turns 'GIT' into 'Git', the second one turns selected 'git' into 'Git'), and merge the result to 'next'.