From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <bruce.richardson@intel.com> Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 158B2952; Tue, 21 Feb 2017 15:16:01 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Feb 2017 06:16:01 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,189,1484035200"; d="scan'208";a="227932170" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.61]) by fmsmga004.fm.intel.com with SMTP; 21 Feb 2017 06:15:59 -0800 Received: by (sSMTP sendmail emulation); Tue, 21 Feb 2017 14:15:58 +0000 Date: Tue, 21 Feb 2017 14:15:58 +0000 From: Bruce Richardson <bruce.richardson@intel.com> To: Thomas Monjalon <thomas.monjalon@6wind.com> Cc: dev@dpdk.org, techboard@dpdk.org Message-ID: <20170221141558.GA208988@bricha3-MOBL3.ger.corp.intel.com> References: <1487678567-13375-1-git-send-email-bruce.richardson@intel.com> <5210332.Rcp5tEyIor@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5210332.Rcp5tEyIor@xps13> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.7.2 (2016-11-26) Subject: Re: [dpdk-dev] [PATCH] doc: add details on requirements for patch ack and merge X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 21 Feb 2017 14:16:02 -0000 On Tue, Feb 21, 2017 at 03:12:32PM +0100, Thomas Monjalon wrote: > 2017-02-21 12:02, Bruce Richardson: > > +#. Once a patch has been acked by the relevant maintainer, reviewers may still comment on it for a further > > + two weeks. After that time, the patch should be merged into the relevent git tree for the next release. > > + Additional notes and restrictions: > > + > > + * patches should be acked by a maintainer at least two days before the release merge > > + deadline, in order to make that release. > > + * for patches acked with less than two weeks to go to the merge deadline, all additional > > + comments should be made no later than two days before the merge deadline. > > Do we need a drawing to illustrate the deadlines? :) > > > + * after the appropriate time for additional feedback has passed, if the patch has not yet > > + been merged to the relevant tree by the committer, it should be treated as though it had, > > + in that any additional changes needed to it must be addressed by a follow-on patch, rather > > + than rework of the original. > > + * trivial patches may be merged sooner than described above at the tree committer's > > + discretion. > > Is it a trivial patch or should I wait 2 weeks before merging this one? The "trivial" is up to you as committer. The 2 weeks depends on when John acks it as docs maintainer. :-P > > Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com> >