From mboxrd@z Thu Jan  1 00:00:00 1970
From: Panu Matilainen <pmatilai@redhat.com>
Subject: Re: DPDK patch backlog
Date: Wed, 21 Oct 2015 11:48:13 +0300
Message-ID: <5627514D.1010103@redhat.com>
References: <20151015144406.1aaca698@xeon-e3>
 <20151020213424.696541ad@xeon-e3> <2717598.bIV87FGGpb@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
 Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 9F8379378
 for <dev@dpdk.org>; Wed, 21 Oct 2015 10:48:15 +0200 (CEST)
In-Reply-To: <2717598.bIV87FGGpb@xps13>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 10/21/2015 11:25 AM, Thomas Monjalon wrote:
> 2015-10-20 21:34, Stephen Hemminger:
>> Patch backlog is not getting better, now at 486.
>>
>> How can we break this logjam?
>> Do I need to make a new "ready for merge" tree?
>
> What would mean "ready for merge"?
> A lot of patches are acked but do not compile or doc is missing.

Well, isn't that one quite reasonable definition of being "ready"?
- patch must be acked
- patch must apply and compile (when relevant)
- is appropriately documented (commit message style and all)

- Panu -

>
> I have the feeling it would become easier if there were mailing-list, patchwork
> and git tree dedicated to some areas. What about starting with drivers/net?
>