From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
Date: Thu, 15 Jan 2015 04:27:03 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511974575@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7E89FD@SHSMSX104.ccr.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhang, Helin
> Sent: Thursday, January 15, 2015 12:15 PM
> To: Neil Horman; Stephen Hemminger
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
>
> +1, Some patch set might be ready for being merged.
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman
> > Sent: Thursday, January 15, 2015 5:02 AM
> > To: Stephen Hemminger
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
> >
> > On Wed, Jan 14, 2015 at 12:23:52PM -0800, Stephen Hemminger wrote:
> > > Ok, so 1.8.0 came out almost a month ago and none of the patches
> > > that were deferred waiting for the release got merged since then.
> > > Last commit in git is the 1.8.0 release.
> > >
> > > Where is the post-merge window bundle, where are the later commits?
> > > Lots of patches are sitting rotting in patchwork...
> > >
> > >
> >
> > +1, I've had the same questions.
> > Neil
+1, the earlier some patches are merged into mainline, and the easier those sequent patch sets can resolve their conflicts.
Thanks
Changchun
next prev parent reply other threads:[~2015-01-15 4:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 20:23 Stephen Hemminger
2015-01-14 21:01 ` Neil Horman
2015-01-15 4:15 ` Zhang, Helin
2015-01-15 4:27 ` Ouyang, Changchun [this message]
2015-01-15 9:51 ` Thomas Monjalon
2015-01-15 13:06 ` Neil Horman
2015-01-15 17:25 ` Thomas Monjalon
2015-01-15 18:51 ` Neil Horman
2015-01-15 21:55 ` O'driscoll, Tim
2015-01-16 1:46 ` Matthew Hall
2015-01-16 7:16 ` Thomas Monjalon
2015-01-16 16:51 ` Neil Horman
2015-01-17 19:57 ` O'driscoll, Tim
2015-01-18 0:30 ` Stephen Hemminger
[not found] ` <20150118182508.GA21891@hmsreliant.think-freely.org>
2015-01-18 21:48 ` O'driscoll, Tim
2015-01-19 13:30 ` Neil Horman
2015-01-15 22:23 ` Thomas Monjalon
2015-01-16 17:20 ` Neil Horman
2015-01-16 18:18 ` Thomas Monjalon
2015-01-16 18:58 ` Matthew Hall
2015-01-16 20:00 ` Neil Horman
2015-01-16 20:38 ` Matthew Hall
2015-01-16 21:14 ` Neil Horman
2015-01-16 22:43 ` Matthew Hall
2015-01-16 19:53 ` Neil Horman
2015-01-16 14:51 ` Marc Sune
2015-01-16 16:56 ` Neil Horman
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=F52918179C57134FAEC9EA62FA2F962511974575@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=stephen@networkplumber.org \
/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).