From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: Status of devel/netback.liu.v5.on.3.5 branch
Date: Thu, 31 May 2012 12:12:40 -0400 [thread overview]
Message-ID: <20120531161240.GB13939@phenom.dumpdata.com> (raw)
In-Reply-To: <1338479555.17466.18.camel@zakaz.uk.xensource.com>
On Thu, May 31, 2012 at 04:52:35PM +0100, Ian Campbell wrote:
> On Thu, 2012-05-31 at 16:39 +0100, Konrad Rzeszutek Wilk wrote:
> > On Thu, May 31, 2012 at 05:39:30PM +0200, Sander Eikelenboom wrote:
> > > Hi Konrad,
> > >
> > > What is the status of the "devel/netback.liu.v5.on.3.5" branch in your tree ?
> >
> > Hm, lets wrap Ian and CC in this converstation. Were there
> > any big outstanding TODOs before the network maintainer
> > was OK with them?
>
> IIRC all of Wei's patches were RFC and not yet intended for upstreaming
> yet, there was other work we wanted to do first to validate and round
> out the ideas started by those patches before committing to them..
>
> > > It doesn't seem to be destined for 3.5 mainline yet ?
>
> No it isn't.
>
> This is a branch containing some development patches which Wei sent out,
> it's not even Wei's own development branch.
Where is his git tree?
>
> Ian.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-31 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <187649850.20120531173930@eikelenboom.it>
2012-05-31 15:39 ` Status of devel/netback.liu.v5.on.3.5 branch Konrad Rzeszutek Wilk
2012-05-31 15:52 ` Ian Campbell
2012-05-31 16:12 ` Konrad Rzeszutek Wilk [this message]
2012-05-31 16:24 ` Ian Campbell
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=20120531161240.GB13939@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=linux@eikelenboom.it \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.