From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: vascomalmeida@sapo.pt, gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH 5/5] unpack-trees: do not capitalize "working"
Date: Thu, 08 Sep 2016 08:36:27 +0200 [thread overview]
Message-ID: <vpqa8fiaoes.fsf@anie.imag.fr> (raw)
In-Reply-To: <20160908043453.6044-1-alexhenrie24@gmail.com> (Alex Henrie's message of "Wed, 7 Sep 2016 22:34:53 -0600")
Alex Henrie <alexhenrie24@gmail.com> writes:
> In English, only proper nouns are capitalized.
>
> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
> unpack-trees.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/unpack-trees.c b/unpack-trees.c
> index 11c37fb..c87a90a 100644
> --- a/unpack-trees.c
> +++ b/unpack-trees.c
> @@ -123,9 +123,9 @@ void setup_unpack_trees_porcelain(struct unpack_trees_options *opts,
> msgs[ERROR_SPARSE_NOT_UPTODATE_FILE] =
> _("Cannot update sparse checkout: the following entries are not up-to-date:\n%s");
> msgs[ERROR_WOULD_LOSE_ORPHANED_OVERWRITTEN] =
> - _("The following Working tree files would be overwritten by sparse checkout update:\n%s");
> + _("The following working tree files would be overwritten by sparse checkout update:\n%s");
> msgs[ERROR_WOULD_LOSE_ORPHANED_REMOVED] =
> - _("The following Working tree files would be removed by sparse checkout update:\n%s");
> + _("The following working tree files would be removed by sparse checkout update:\n%s");
Probably a leftover from an old sentence starting with Working? In any
case, obviously correct too, thanks.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2016-09-08 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 4:34 [PATCH 5/5] unpack-trees: do not capitalize "working" Alex Henrie
2016-09-08 6:36 ` Matthieu Moy [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqa8fiaoes.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vascomalmeida@sapo.pt \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.