From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 23A10A046B for <public@inbox.dpdk.org>; Mon, 22 Jul 2019 15:56:40 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9CB741BE4A; Mon, 22 Jul 2019 15:56:39 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id B61921B197 for <dev@dpdk.org>; Mon, 22 Jul 2019 15:56:37 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jul 2019 06:56:36 -0700 X-IronPort-AV: E=Sophos;i="5.64,295,1559545200"; d="scan'208";a="169258739" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.51]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jul 2019 06:56:35 -0700 Date: Mon, 22 Jul 2019 14:56:32 +0100 From: Bruce Richardson <bruce.richardson@intel.com> To: Ferruh Yigit <ferruh.yigit@intel.com> Cc: Thomas Monjalon <thomas@monjalon.net>, "Singh, Jasvinder" <jasvinder.singh@intel.com>, "dev@dpdk.org" <dev@dpdk.org>, "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> Message-ID: <20190722135632.GD289@bricha3-MOBL.ger.corp.intel.com> References: <20190719141825.101844-2-jasvinder.singh@intel.com> <4378606.kpYsyM8nYf@xps> <54CBAA185211B4429112C315DA58FF6D3FD9D18A@IRSMSX103.ger.corp.intel.com> <3201074.5HFWSc9n9k@xps> <802ca1df-bfec-0255-bd51-56ceedc47558@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <802ca1df-bfec-0255-bd51-56ceedc47558@intel.com> User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-dev] [PATCH v7 00/11] sched: feature enhancements X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> On Mon, Jul 22, 2019 at 02:53:04PM +0100, Ferruh Yigit wrote: > On 7/22/2019 2:33 PM, Thomas Monjalon wrote: > > 22/07/2019 15:22, Singh, Jasvinder: > >> From: Thomas Monjalon [mailto:thomas@monjalon.net] > >>> PS: please make all versions replying to the cover letter of v1. > >> > >> For sending new version, followed suggestion from Ferruh by replying to previous version, not the first version. > > > > Replying to previous version creates an unneeded indentation. > > And, as you are replying to first patch (not cover letter), > > it makes new version in the middle of the previous one. > > > > Ahh, as Jasvinder said, I was always suggesting replying to first mail of the > previous version. As long as agreed on one, I don't really mind one against other. > > What is the rule now, a new version replied to first mail of *first* version? I would not use the term "first mail" as that is ambiguous and could imply the first patch. I always try and reply to the cover letter of the v1. That keeps things in thread without a new level of indentation each subsequent version.