From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK patch backlog
Date: Wed, 21 Oct 2015 07:10:50 -0400 [thread overview]
Message-ID: <20151021111050.GA10645@hmsreliant.think-freely.org> (raw)
In-Reply-To: <2717598.bIV87FGGpb@xps13>
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?
>
>
prev parent reply other threads:[~2015-10-21 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 21:44 Stephen Hemminger
2015-10-16 2:47 ` Zhu, Heqing
2015-10-16 13:08 ` Lu, Wenzhuo
2015-10-16 8:45 ` Thomas Monjalon
2015-10-16 14:25 ` Neil Horman
2015-10-22 1:35 ` Qiu, Michael
2015-10-21 4:34 ` Stephen Hemminger
2015-10-21 8:25 ` Thomas Monjalon
2015-10-21 8:48 ` Panu Matilainen
2015-10-21 9:03 ` Thomas Monjalon
2015-10-21 17:41 ` Matthew Hall
2015-10-23 21:39 ` Thomas Monjalon
2015-10-22 1:45 ` Qiu, Michael
2015-10-21 11:10 ` Neil Horman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151021111050.GA10645@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).