All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Ceph updates for 5.5-rc1
Date: Fri, 6 Dec 2019 12:05:01 +0100	[thread overview]
Message-ID: <CAOi1vP_biwOVuG9U4nemfH803O_ADHGgjmd0_6eL-ZJhyrkOYA@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wjm+9rJvh=aRahfoN7z6waV87Eqr=-i_Cb7zOwHrugf5A@mail.gmail.com>

On Thu, Dec 5, 2019 at 10:19 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Wed, Dec 4, 2019 at 12:02 PM Ilya Dryomov <idryomov@gmail.com> wrote:
> >
> > Colin Ian King (1):
> >       rbd: fix spelling mistake "requeueing" -> "requeuing"
>
> Hmm. Why? That's not a spelling mistake, it's the same word.
>
> Arguably "requeue" isn't much of a real word to begin with, and is
> more of a made-up tech language. And then on wiktionary apparently the
> only "ing" form you find is the one without the final "e", but
> honestly, that's reaching. The word doesn't exist in _real_
> dictionaries at all.
>
> I suspect "re-queueing" with the explicit hyphen would be the more
> legible spelling (with or without the "e" - both forms are as
> correct), but whatever.
>
> I've pulled it, but I really don't think it was misspelled to begin
> with, and somebody who actually cares about language probably wouldn't
> like either form.

FWIW that was my spelling.  I suspected the same thing, saw it being
used in various spellings, but since Colin is a native speaker I took
the patch.

Thanks,

                Ilya

  reply	other threads:[~2019-12-06 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 20:03 [GIT PULL] Ceph updates for 5.5-rc1 Ilya Dryomov
2019-12-05 21:19 ` Linus Torvalds
2019-12-06 11:05   ` Ilya Dryomov [this message]
2019-12-05 21:30 ` pr-tracker-bot

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=CAOi1vP_biwOVuG9U4nemfH803O_ADHGgjmd0_6eL-ZJhyrkOYA@mail.gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.