From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Ben Guthro <bguthro@virtualiron.com>
Subject: Re: 3.1.1 RC4?
Date: Tue, 9 Oct 2007 10:03:12 +0200 [thread overview]
Message-ID: <200710091003.13250.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C330F362.E971%Keir.Fraser@cl.cam.ac.uk>
On Tuesday 09 October 2007 09:59:14 Keir Fraser wrote:
> On 8/10/07 20:13, "Ben Guthro" <bguthro@virtualiron.com> wrote:
> > I noticed that a Shadow patch went into the 3.1.1 staging tree today.
> > Does this mean that we should expect a 4th release candidate before the
> > 3.1.1 release tag is official?
> >
> > If so - how much testing time are you going to give that release
> > candidate before deciding whether a release tag, or another RC round is
> > appropriate?
>
> Actually I don't plan to do another -rc round just for that one. It's an
> obvious bug fix.
Maybe you will or have to for security reasons:
http://secunia.com/advisories/26986/
1) has been fixed, 2) 3) and 4) are qemu related and impact
Xen through ioemu in the tools.
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2007-10-09 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 19:13 3.1.1 RC4? Ben Guthro
2007-10-09 7:59 ` Keir Fraser
2007-10-09 8:03 ` Christoph Egger [this message]
2007-10-09 8:17 ` Keir Fraser
2007-10-09 8:31 ` Christoph Egger
2007-10-09 9:00 ` 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=200710091003.13250.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=bguthro@virtualiron.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.