From: "Ondřej Bílka" <neleai@seznam.cz>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: American or British English?
Date: Sat, 20 Jul 2013 22:56:20 +0200 [thread overview]
Message-ID: <20130720205620.GA3825@domone> (raw)
In-Reply-To: <20130720193905.GA3904@vauxhall.crustytoothpaste.net>
On Sat, Jul 20, 2013 at 07:39:06PM +0000, brian m. carlson wrote:
> On Sat, Jul 20, 2013 at 09:13:12PM +0200, Ondřej Bílka wrote:
> > A dictionary that I generated is following, patch is below.
> >
> > alloted allocated
>
> "allotted" is a valid word, and I think it would work fine in the code.
> It's probably what was intended, anyway.
>
OK, I am not native speaker so I sometimes choose simpler variant.
> > behaviour behavior
> > colourful colorful
> > initialised initialized
>
> I'm not sure whether git has a standard for which dialect of English is
> to be used, but the three words on the left are considered correct in
> most non-American dialects. Characterizing them as "typos" isn't
> strictly correct. Perhaps "Convert comments to American English" is
> more accurate?
>
Yeah, on most projects I seen preference for consistently using American
versions. How you decide is matter of preference.
> --
> brian m. carlson / brian with sandals: Houston, Texas, US
> +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
> OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
next prev parent reply other threads:[~2013-07-20 20:56 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 ` Ondřej Bílka [this message]
2013-07-20 19:51 ` Ramkumar Ramachandra
2013-07-20 20:30 ` Ondřej Bílka
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=20130720205620.GA3825@domone \
--to=neleai@seznam.cz \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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.