From: "Ondřej Bílka" <neleai@seznam.cz>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix typos in comments
Date: Sat, 20 Jul 2013 22:30:38 +0200 [thread overview]
Message-ID: <20130720203037.GA3753@domone> (raw)
In-Reply-To: <CALkWK0kzsVLGXZsxWO5rYahb39LSTFvGuE3hZaCgrJ=nuaoo7w@mail.gmail.com>
On Sun, Jul 21, 2013 at 01:21:10AM +0530, Ramkumar Ramachandra wrote:
> Ondřej Bílka wrote:
> > diff --git a/builtin/checkout.c b/builtin/checkout.c
> > index 7fe0bff..9f29bb2 100644
> > --- a/builtin/checkout.c
> > +++ b/builtin/checkout.c
> > @@ -1137,7 +1137,7 @@ int cmd_checkout(int argc, const char **argv, const char *prefix)
> > * 3) git checkout <something> [<paths>]
> > *
> > * including "last branch" syntax and DWIM-ery for names of
> > - * remote branches, erroring out for invalid or ambiguous cases.
> > + * remote branches, erring out for invalid or ambiguous cases.
>
> Didn't look through the entire patch, but this caught me eye: what's
> wrong with "erroring out"?
Well aspell did not know it so I thought that erring is more
appropriate. Now it looks more murky, see
http://english.stackexchange.com/questions/3059/is-errored-correct-usage
I am ok with removing this correction.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-20 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 19:07 [PATCH 1/2] Fix generic typos in comments Ondřej Bílka
2013-07-20 19:13 ` [PATCH 2/2] Fix " Ondřej Bílka
2013-07-20 19:39 ` brian m. carlson
2013-07-20 20:56 ` American or British English? Ondřej Bílka
2013-07-20 19:51 ` [PATCH 2/2] Fix typos in comments Ramkumar Ramachandra
2013-07-20 20:30 ` Ondřej Bílka [this message]
2013-07-21 22:32 ` Junio C Hamano
2013-07-21 22:29 ` [PATCH 1/2] Fix generic " Junio C Hamano
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=20130720203037.GA3753@domone \
--to=neleai@seznam.cz \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).