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 E7F24A04A6; Fri, 7 Jan 2022 17:37:39 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 754BB40143; Fri, 7 Jan 2022 17:37:39 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 260F940042 for ; Fri, 7 Jan 2022 17:37:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1641573457; x=1673109457; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=avawEXetyVSDL+UXLbASmAZ/h1cCW6FMfi6ABx+1U40=; b=hPv2Nyy4mDNWWdBNDOCNXjen0VPSS4CvfRR12dSZPt6BstYKvo2b46kJ /TqYBOTuItY7R3h3oSRkF4fGXueZqZMTFiTRgA1JnltkPU4pfsTnYcx26 HR8AgFP6CVWijgqbRxXJAOZ4VP1XQoG4u1+RCtfZrHjZmuZZdsoAGyW8B yYdtdGzRUyuAKSmDMNN5cvvNqQRjgcBpqj6Xq0PW7Z86LV18DzV6UirP6 4K8FYWulgng37ZPYNKxgBCLzzznKQ/azuMNDFn5A3AXEnzXa9hRDCqtc6 D4KQs4BHzIcl3diVnjxrFUr8wMdgZM2I5bU2WSWNKYoZLjvpEEMGIJH/s A==; X-IronPort-AV: E=McAfee;i="6200,9189,10219"; a="222883943" X-IronPort-AV: E=Sophos;i="5.88,270,1635231600"; d="scan'208";a="222883943" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jan 2022 08:37:34 -0800 X-IronPort-AV: E=Sophos;i="5.88,270,1635231600"; d="scan'208";a="527420011" 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 08:37:33 -0800 Date: Fri, 7 Jan 2022 16:37:29 +0000 From: Bruce Richardson To: Morten =?iso-8859-1?Q?Br=F8rup?= Cc: Thomas Monjalon , 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> <98CBD80474FA8B44BF855DF32C47DC35D86DEE@smartserver.smartshare.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D86DEE@smartserver.smartshare.dk> 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 05:27:55PM +0100, Morten Brørup wrote: > > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > > Sent: Friday, 7 January 2022 16.29 > > > > 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? > > Because they have two different dictionaries: US English and British English. E.g. "color" is correct in one territory, while "colour" is correct in another territory. > > > > > 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". > > Being somewhat a language nerd, I would like to know your opinions about "aging" vs. "ageing", in the context of timing out obsolete entries in e.g. a MAC table? > > Or is "ageing" an action, and "aging" a state? > This is all starting to make my head hurt, because everything is so irregular! In this case I would have tended toward ageing with the "e", and from some quick googling, it appears that this is the more common spelling outside north america. However, unlike queuing, I really don't have strong feelings about the spelling of ag(e)ing. [On the other hand, given my current age, I have very strong feelings of dislike about the concept of ageing itself! :-)] /Bruce