From mboxrd@z Thu Jan  1 00:00:00 1970
From: Neil Horman <nhorman@tuxdriver.com>
Subject: Re: DPDK patch backlog
Date: Wed, 21 Oct 2015 07:10:50 -0400
Message-ID: <20151021111050.GA10645@hmsreliant.think-freely.org>
References: <20151015144406.1aaca698@xeon-e3> <20151020213424.696541ad@xeon-e3>
 <2717598.bIV87FGGpb@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: dev@dpdk.org
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58])
 by dpdk.org (Postfix) with ESMTP id D7F119432
 for <dev@dpdk.org>; Wed, 21 Oct 2015 13:11:04 +0200 (CEST)
Content-Disposition: inline
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 Wed, Oct 21, 2015 at 10:25:12AM +0200, 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.
I would think that many of these patches that don't compile should be marked as
rejected in patchwork, and a note sent to the list.  If you can enable the
patchwork xmlrpc interface, we could script/automate that process


Neil

> 
> 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?
> 
>