From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <michael.qiu@intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id 9CD949356
 for <dev@dpdk.org>; Thu, 22 Oct 2015 03:45:20 +0200 (CEST)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by fmsmga102.fm.intel.com with ESMTP; 21 Oct 2015 18:45:08 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,180,1444719600"; d="scan'208";a="832623266"
Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203])
 by fmsmga002.fm.intel.com with ESMTP; 21 Oct 2015 18:45:08 -0700
Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by
 FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 21 Oct 2015 18:45:08 -0700
Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by
 FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 21 Oct 2015 18:45:08 -0700
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.96]) by
 shsmsx102.ccr.corp.intel.com ([169.254.2.253]) with mapi id 14.03.0248.002;
 Thu, 22 Oct 2015 09:45:06 +0800
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, Panu Matilainen
 <pmatilai@redhat.com>
Thread-Topic: [dpdk-dev] DPDK patch backlog
Thread-Index: AQHRB5K1+WDfX5i29EWaqsJMVTDP1Q==
Date: Thu, 22 Oct 2015 01:45:06 +0000
Message-ID: <533710CFB86FA344BFBF2D6802E6028621B5023F@SHSMSX101.ccr.corp.intel.com>
References: <20151015144406.1aaca698@xeon-e3> <2717598.bIV87FGGpb@xps13>
 <5627514D.1010103@redhat.com> <2265365.ZSeGOJNMlR@xps13>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK patch backlog
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <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: Thu, 22 Oct 2015 01:45:21 -0000

On 2015/10/21 17:05, Thomas Monjalon wrote:=0A=
> 2015-10-21 11:48, Panu Matilainen:=0A=
>> On 10/21/2015 11:25 AM, Thomas Monjalon wrote:=0A=
>>> 2015-10-20 21:34, Stephen Hemminger:=0A=
>>>> Patch backlog is not getting better, now at 486.=0A=
>>>>=0A=
>>>> How can we break this logjam?=0A=
>>>> Do I need to make a new "ready for merge" tree?=0A=
>>> What would mean "ready for merge"?=0A=
>>> A lot of patches are acked but do not compile or doc is missing.=0A=
>> Well, isn't that one quite reasonable definition of being "ready"?=0A=
>> - patch must be acked=0A=
>> - patch must apply and compile (when relevant)=0A=
>> - is appropriately documented (commit message style and all)=0A=
> Yes.=0A=
> Compilation must be tested with GCC and clang, as static and shared libra=
ries=0A=
> and for 32-bit and 64-bit targets.=0A=
> Documented means good commit message and doc or release notes updated.=0A=
=0A=
What about bug fix patches?=0A=
=0A=
Thanks,=0A=
Michael=0A=
>=0A=
=0A=