git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Todd Zullinger <tmz@pobox.com>,
	Nanako Shiraishi <nanako3@lavabit.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Fix overridable written with an extra 'e'
Date: Fri, 28 Aug 2009 15:15:29 +0000	[thread overview]
Message-ID: <32541b130908280815y78f95140re679c336fbd17443@mail.gmail.com> (raw)
In-Reply-To: <7v63c8a69a.fsf@alter.siamese.dyndns.org>

On Fri, Aug 28, 2009 at 4:53 AM, Junio C Hamano<gitster@pobox.com> wrote:
> Hmph, I don't know.  Googling "overrideable" suggests "Did you mean
> overridable?" which is enough clue for me.

Using a similar system, the Google hit count:

overrideable: 26,900
overridable: 339,000
overridden: 2,280,000

Which agrees with my intuition that you can get away with overridable,
but it's much more common to just use overridden.

"override" of course comes from "ride" (181,000,000).  A horse can be
ridden (10,500,000) if it's ridable (82,500).

The bad news: rideable (201,000).

http://www.merriam-webster.com/dictionary/ridable shows rideable as
the preferred spelling, but accepts both.

Have fun,

Avery

  reply	other threads:[~2009-08-28 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  3:18 [PATCH] Fix overridable written with an extra 'e' Nanako Shiraishi
2009-08-28  3:43 ` Todd Zullinger
2009-08-28  4:53   ` Junio C Hamano
2009-08-28 15:15     ` Avery Pennarun [this message]
2009-08-28 15:31       ` Johannes Schindelin
2009-08-30 17:58   ` Uri Okrent

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=32541b130908280815y78f95140re679c336fbd17443@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@lavabit.com \
    --cc=tmz@pobox.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.
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).