From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Neil Horman <nhorman@tuxdriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] Patches outstanding
Date: Thu, 19 Feb 2015 15:15:47 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54CCFAF1@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <3427184.DR4H9RgUjS@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, February 19, 2015 1:47 PM
> To: Neil Horman
> Cc: dev@dpdk.org; Stephen Hemminger
> Subject: Re: [dpdk-dev] Patches outstanding
>
> 2015-02-19 08:08, Neil Horman:
> > On Tue, Feb 17, 2015 at 10:35:07AM -0500, Stephen Hemminger wrote:
> > > There are currently 1039 patches outstanding on DPDK.
> > > What is the schedule for getting these merged or resolved?
> > > I don't think it would be reasonable to declare 2.0 as done
> > > until the patch backlog is 0!
> > >
> >
> > I think the subtrees were supposed to start biting into this, but I don't see
> > them getting used yet.
>
> Yes
> Actually the main problem is still on reviews.
> There are more good reviews in this cycle.
> But some patchset are not reviewed and some others are acked
> without being carefully reviewed.
Progress on reviews has been a little slow on our side. One of the reasons for this is that our PRC team are on their new year holidays at the moment, so we're a little short staffed. They return to the office in the middle of next week, after which we'll be back to full strength.
We do agree with Thomas on the need for thorough reviews. We're working on this, so you should see more reviews/acknowledgements soon.
Tim
prev parent reply other threads:[~2015-02-19 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 15:35 Stephen Hemminger
2015-02-17 15:59 ` Thomas Monjalon
2015-02-19 13:08 ` Neil Horman
2015-02-19 13:46 ` Thomas Monjalon
2015-02-19 15:15 ` O'driscoll, Tim [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=26FA93C7ED1EAA44AB77D62FBE1D27BA54CCFAF1@IRSMSX102.ger.corp.intel.com \
--to=tim.o'driscoll@intel.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=shemming@brocade.com \
--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).