From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Josh Soref <jsoref@gmail.com>,
dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v2] Spelling comments/text
Date: Fri, 07 Jan 2022 15:58:27 +0100 [thread overview]
Message-ID: <820785518.0ifERbkFSE@thomas> (raw)
In-Reply-To: <YdgiyTjtFohadpWd@bricha3-MOBL.ger.corp.intel.com>
07/01/2022 12:23, Bruce Richardson:
> On Thu, Jan 06, 2022 at 05:52:49PM +0100, Thomas Monjalon wrote:
> > 29/11/2021 17:08, Josh Soref:
> > > - * dequeueing once we've filled up the queue, we have to benchmark it
> > > + * dequeuing once we've filled up the queue, we have to benchmark it
> >
> > I think "dequeueing" is correct.
> >
> Well, we have "queue" and "queuing" so therefore I would expect the "e" to
> be similarly dropped from the "dequeue" version.
When looking on Internet, queueing is preffered over queuing.
https://dictionary.cambridge.org/dictionary/english/queueing
https://english.stackexchange.com/questions/60852/queueing-or-queuing
Best justification: five vowels in a row!
Why English people cannot agree on how to write words?
Let's all use French, it's simpler :)
next prev parent reply other threads:[~2022-01-07 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 19:58 [PATCH] Spelling Josh Soref
2021-11-29 12:49 ` Ferruh Yigit
2021-11-29 13:59 ` Bruce Richardson
2021-11-29 14:02 ` Thomas Monjalon
2021-11-29 18:11 ` Ajit Khaparde
2021-11-29 14:03 ` Ferruh Yigit
2021-11-29 14:12 ` Josh Soref
2021-11-29 14:47 ` Bruce Richardson
2021-11-29 14:52 ` Ferruh Yigit
2021-11-29 16:08 ` [PATCH v2] Spelling comments/text Josh Soref
2022-01-06 16:46 ` Thomas Monjalon
2022-01-11 10:51 ` Thomas Monjalon
2022-01-11 14:00 ` Kevin Traynor
2022-01-11 14:23 ` Thomas Monjalon
2022-01-06 16:52 ` Thomas Monjalon
2022-01-07 11:23 ` Bruce Richardson
2022-01-07 14:58 ` Thomas Monjalon [this message]
2022-01-07 15:04 ` Josh Soref
2022-01-07 15:28 ` Bruce Richardson
2022-01-07 16:27 ` Morten Brørup
2022-01-07 16:37 ` Bruce Richardson
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=820785518.0ifERbkFSE@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jsoref@gmail.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 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.