From: Keir Fraser <keir.fraser@eu.citrix.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] Re: New release candidate for Xen 4.0.1
Date: Wed, 21 Jul 2010 11:23:10 +0100 [thread overview]
Message-ID: <C86C891E.1B38C%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1007211039060.8852@algedi.dur.ac.uk>
On 21/07/2010 10:42, "M A Young" <m.a.young@durham.ac.uk> wrote:
> On Tue, 20 Jul 2010, Keir Fraser wrote:
>
>> Shouldn't this be in xen-unstable first, and then backported in the usual
>> way?
>
> If that is the normal process then yes. I haven't checked whether this
> bug exists in xen-unstable, but a quick glance at the Makefile I am
> patching suggests that it probably does.
The precise process for toolset patches now is that they get applied to
http://xenbits.xen.org/staging/xen-unstable-tools.hg by Ian Jackson or
Stefano Stabellini. I merge that tree into main xen-unstable.hg nearly every
day. Then, for 4.0.x and 3.4.x stable branches, Ian and Stefano nominate
patches for backport from xen-unstable.
-- Keir
> Michael Young
next prev parent reply other threads:[~2010-07-21 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 18:01 [PATCH] Re: New release candidate for Xen 4.0.1 M A Young
2010-07-20 18:32 ` Keir Fraser
2010-07-21 9:42 ` M A Young
2010-07-21 10:23 ` Keir Fraser [this message]
2010-07-21 16:30 ` Dan Magenheimer
2010-07-21 16:46 ` Keir Fraser
2010-07-23 15:49 ` Ian Jackson
2010-07-21 11:53 ` Stefano Stabellini
2010-07-21 12:08 ` M A Young
2010-07-21 12:14 ` Stefano Stabellini
2010-07-21 12:48 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-07-16 13:05 Keir Fraser
2010-07-16 19:29 ` [PATCH] " M A Young
2010-07-20 12:01 ` Pasi Kärkkäinen
2010-07-20 12:30 ` 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=C86C891E.1B38C%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=m.a.young@durham.ac.uk \
--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).