From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 651C6A04A6; Fri, 7 Jan 2022 16:29:01 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0053940140; Fri, 7 Jan 2022 16:29:01 +0100 (CET) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mails.dpdk.org (Postfix) with ESMTP id E282540042 for ; Fri, 7 Jan 2022 16:28:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1641569339; x=1673105339; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=7E8WZWEpag+31XZNSyTRWSIdvDD/q21I6zGrXq2CB7A=; b=cYGXl61YFvRUMxUJjLAIW0WWnvyiiJ5+MFjTf0QWru04V6uzfX0AfpcT OHtARpVqjJKKzZr7tQEKI/y7XR208asxQnhD1MGbxMyvlwCC0WBXV3663 Bwm0jJdIjhm5gDf6D8fZO1s0c2gLw6WcQ41m4Af5JTCbmQfuuKwedbv9I zIVZa4SvtKFauf/ZbLVyS0hEgA9oDg6WxuudoeefB94a3yD0Bt1l8G320 PNPO7EbhGkbji4G9863/+RfrUi1KmPIN+KNqLnNd3paRlEx7r7H9UcxuO 85+1fuCG2XaP/fWH4mrEjzqHKL2Abp/2WFtcdXMrd7iGjXaTaeG1Grfn8 w==; X-IronPort-AV: E=McAfee;i="6200,9189,10219"; a="240432192" X-IronPort-AV: E=Sophos;i="5.88,270,1635231600"; d="scan'208";a="240432192" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jan 2022 07:28:57 -0800 X-IronPort-AV: E=Sophos;i="5.88,270,1635231600"; d="scan'208";a="527399066" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.26.15]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 07 Jan 2022 07:28:55 -0800 Date: Fri, 7 Jan 2022 15:28:52 +0000 From: Bruce Richardson To: Thomas Monjalon Cc: Josh Soref , dev@dpdk.org, Ferruh Yigit , David Marchand Subject: Re: [PATCH v2] Spelling comments/text Message-ID: References: <20211126195851.50167-1-jsoref@users.noreply.github.com> <1848208.taCxCBeP46@thomas> <820785518.0ifERbkFSE@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <820785518.0ifERbkFSE@thomas> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, Jan 07, 2022 at 03:58:27PM +0100, Thomas Monjalon wrote: > 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? Being Irish, I'm not sure I can answer that! :-) My preference here is the shorter "queuing" version suggested, and it was what dictionary.com suggested under "queue" entry. My preference is largely based on consistency with other words which end in "ue": "argue" -> "arguing", "accrue" -> "accruing". > Let's all use French, it's simpler :) > I don't think I have enough accent keys on my keyboard :-)