git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Pablo Santiago Blum de Aguiar <scorphus@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH] git-cherry-pick.txt: correct a small typo
Date: Sun, 29 May 2016 17:41:33 -0700	[thread overview]
Message-ID: <xmqq4m9gpebm.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160529192929.40200-1-scorphus@gmail.com> (Pablo Santiago Blum de Aguiar's message of "Sun, 29 May 2016 16:29:29 -0300")

Pablo Santiago Blum de Aguiar <scorphus@gmail.com> writes:

> Most of the document mentions `behavior` instead of the British
> variation, `behaviour`. This change makes it consistent.
>
> Signed-off-by: Pablo Santiago Blum de Aguiar <scorphus@gmail.com>
> ---

Thanks.  This line comes from an ancient 4bee9584 (cherry-pick: add
--allow-empty-message option, 2012-08-02) that happend in v1.8.0
timeframe, and nobody complained for the last 4 years ;-)

We see this in CodingGuidelines:

 The documentation liberally mixes US and UK English (en_US/UK)
 norms for spelling and grammar, which is somewhat unfortunate.
 In an ideal world, it would have been better if it consistently
 used only one and not the other, and we would have picked en_US
 (if you wish to correct the English of some of the existing
 documentation, please see the documentation-related advice in the
 Documentation/SubmittingPatches file).

and the part of SubmittingPatches it refers to is this:

 Speaking of the documentation, it is currently a liberal mixture of US
 and UK English norms for spelling and grammar, which is somewhat
 unfortunate.  A huge patch that touches the files all over the place
 only to correct the inconsistency is not welcome, though.  Potential
 clashes with other changes that can result from such a patch are not
 worth it.  We prefer to gradually reconcile the inconsistencies in
 favor of US English, with small and easily digestible patches, as a
 side effect of doing some other real work in the vicinity (e.g.
 rewriting a paragraph for clarity, while turning en_UK spelling to
 en_US).  Obvious typographical fixes are much more welcomed ("teh ->
 "the"), preferably submitted as independent patches separate from
 other documentation changes.

I wish there were some "other real work in the vicinity" I can use
as an excuse, which would have made it far easier to take this patch;
as I already took a look at it and wrote a response to it, I'll
queue it anyway ;-)

Thanks.




>  Documentation/git-cherry-pick.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
> index 6154e57..c104a59 100644
> --- a/Documentation/git-cherry-pick.txt
> +++ b/Documentation/git-cherry-pick.txt
> @@ -128,7 +128,7 @@ effect to your index in a row.
>  
>  --allow-empty-message::
>  	By default, cherry-picking a commit with an empty message will fail.
> -	This option overrides that behaviour, allowing commits with empty
> +	This option overrides that behavior, allowing commits with empty
>  	messages to be cherry picked.
>  
>  --keep-redundant-commits::

      reply	other threads:[~2016-05-30  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 19:29 [PATCH] git-cherry-pick.txt: correct a small typo Pablo Santiago Blum de Aguiar
2016-05-30  0:41 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq4m9gpebm.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=scorphus@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).