xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Keir Fraser <keir@xen.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"W. Michael Petullo" <mike@flyn.org>
Subject: Re: Proposal: vif-local [and 1 more messages]
Date: Tue, 24 May 2011 18:51:21 +0100	[thread overview]
Message-ID: <1306259481.7348.1.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <19931.60302.515178.887806@mariner.uk.xensource.com>

On Tue, 2011-05-24 at 18:31 +0100, Ian Jackson wrote:
> W. Michael Petullo writes ("Re: [Xen-devel] Re: New 4.0.2 and 4.1.1 release candidates"):
> > Is it too late to merge the patch discussed at
> >   http://lists.xensource.com/archives/html/xen-devel/2011-05/msg00306.html
> 
> We don't generally apply patches directly to the stable trees (4.0 and
> 4.1, at the moment).  We like them to come through xen-unstable first.
> 
> When you submitted your patch, you got this reply:
> 
> Ian Campbell writes ("Re: [Xen-devel] Proposal: vif-local"):
> > On Mon, 2011-05-09 at 18:10 +0100, W. Michael Petullo wrote:
> > > Allow for site-specific hooks that will be executed after Xen initializes
> > > a vif. This allows an administrator to specify custom firewall rules or
> > > other special configuration parameters.
> > > 
> > > Signed-off-by: W. Michael Petullo <mike@flyn.org>
> > 
> > This is against 4.1? can you check that it applies to xen-unstable.hg
> > please, other than that:
> > 
> > Acked-by: Ian Campbell <ian.campbell@citrix.com>
> 
> Can you confirm that your patch applies and works correctly against
> xen-unstable.hg ?

Michael replied to this mail in <20110510160631.GA17482@imp.local>:

> I pulled xen-unstable.hg from Mercurial and the patch applied cleanly.
> The modified scripts were identical to those resulting from applying
> the patch against 4.1.0.

Ian.

  reply	other threads:[~2011-05-24 17:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21  7:04 New 4.0.2 and 4.1.1 release candidates Keir Fraser
2011-05-24  7:24 ` Keir Fraser
2011-05-24 14:17   ` W. Michael Petullo
2011-05-05 17:15     ` Proposal: vif-local W. Michael Petullo
2011-05-06  8:42       ` Ian Campbell
2011-05-06 17:06         ` W. Michael Petullo
2011-05-09  8:45           ` Ian Campbell
2011-05-09 17:10             ` W. Michael Petullo
2011-05-10  8:02               ` Ian Campbell
2011-05-10 16:06                 ` W. Michael Petullo
2011-05-10 16:12                   ` Ian Campbell
2011-05-24 17:31                 ` Proposal: vif-local [and 1 more messages] Ian Jackson
2011-05-24 17:51                   ` Ian Campbell [this message]
2011-05-25  9:45                     ` Ian Jackson
2011-05-24 15:49     ` Re: New 4.0.2 and 4.1.1 release candidates Keir Fraser
2011-05-24 16:13 ` Olaf Hering
2011-05-24 17:58   ` Keir Fraser
2011-05-24 18:25     ` Olaf Hering
2011-05-24 20:04       ` Keir Fraser
2011-05-26  8:36     ` George Dunlap
2011-05-26  9:09       ` Keir Fraser

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=1306259481.7348.1.camel@dagon.hellion.org.uk \
    --to=ian.campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=mike@flyn.org \
    --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 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).