From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged
Date: Tue, 3 Sep 2013 15:34:08 +0100 [thread overview]
Message-ID: <5225F360.8080706@citrix.com> (raw)
In-Reply-To: <21029.49764.73551.462484@mariner.uk.xensource.com>
On 03/09/13 12:05, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [Xen-devel] Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged"):
>> On 30/08/13 11:14, Jan Beulich wrote:
>> Can I strongly recommend 704302ce9404c73cfb687d31adcf67094ab5bb53
>> "oxenstored: Protect oxenstored from malicious domains." for backport to
>> all trees.
> Done (to 4.3, 4.2, 4.1).
>
> Ian.
Further to this, can I recommend
* 258d27a1d9fb33a490bef1381f52d522225c3dca "pygrub: add Debian
extlinux.conf path"
* d513814db6af2b298b8776d7ffc5fb1261e176f4 "pygrub/GrubConf: fix boot
problem for fedora 19 grub.cfg"
* e892ab5ad4238efc1c425ac7a28581c116e674af "pygrub: add fedora 19
grub.cfg example"
Which are all pygrub fixes for booting newer PV guests.
~Andrew
next prev parent reply other threads:[~2013-09-03 14:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 10:14 Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged Jan Beulich
2013-09-02 18:17 ` Andrew Cooper
2013-09-03 11:05 ` Ian Jackson
2013-09-03 14:34 ` Andrew Cooper [this message]
2013-09-03 14:48 ` Ian Jackson
2013-09-03 14:58 ` Ian Campbell
2013-09-03 15:36 ` Lars Kurth
2013-09-04 8:03 ` Jan Beulich
2013-09-04 10:33 ` Ian Jackson
2013-09-06 12:31 ` Lars Kurth
2013-09-06 12:38 ` Jan Beulich
2013-09-04 7:10 ` Jan Beulich
2013-09-12 9:11 ` Jan Beulich
2013-09-26 8:08 ` Ping: backport proposals (was: Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged) Jan Beulich
2013-09-26 9:31 ` Ping: backport proposals Andrew Cooper
2013-09-26 10:08 ` Jan Beulich
2013-09-27 8:34 ` Jan Beulich
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=5225F360.8080706@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 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.