From: "Jan Beulich" <JBeulich@suse.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: preparations for 4.4.1, 4.3.3, and 4.2.5
Date: Tue, 27 May 2014 10:23:43 +0100 [thread overview]
Message-ID: <538475BF0200007800015ECC@mail.emea.novell.com> (raw)
In-Reply-To: <20140527074413.GA16088@aepfle.de>
>>> On 27.05.14 at 09:44, <olaf@aepfle.de> wrote:
> On Mon, May 19, Jan Beulich wrote:
>
>> with the aim of releasing 4.4.1 no later than 3 months after the original
>> 4.4.0 release, and - in order to consolidate effort as well as to not
>> exceed the 3 month step by too much - 4.3.3 and 4.2.5, please point
>> out to the relevant maintainers any backport requests you may observe
>> still missing but required on the respective branches.
>
> 9011c26 xend/pvscsi: recognize also SCSI CDROM devices
> 2256f09 tools/xend: move assert to exception block
For both this and ...
> 4.2 lacks this xend patch:
>
> 4b5059b xend: Only add cpuid and cpuid_check to sexpr once
... this you should have pinged IanJ instead of me. Cc-ing him now.
Also, a little bit of justification - namely for xend patches - might
help in evaluating whether such proposals are acceptable.
Jan
next prev parent reply other threads:[~2014-05-27 9:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5379E20E02000078000136E7@mail.emea.novell.com>
2014-05-19 14:12 ` preparations for 4.4.1, 4.3.3, and 4.2.5 Jan Beulich
2014-05-19 14:23 ` Andrew Cooper
2014-05-19 14:30 ` Ian Jackson
2014-05-19 20:14 ` Boris Ostrovsky
2014-05-20 12:28 ` Jan Beulich
2014-05-20 13:31 ` Boris Ostrovsky
2014-05-23 13:47 ` Jan Beulich
2014-05-21 15:03 ` Daniel Kiper
2014-05-21 15:12 ` Jan Beulich
2014-05-30 12:03 ` Daniel Kiper
2014-06-11 19:28 ` Daniel Kiper
2014-10-07 10:04 ` Daniel Kiper
2014-05-27 7:44 ` Olaf Hering
2014-05-27 8:23 ` Olaf Hering
2014-05-27 9:23 ` Jan Beulich [this message]
2014-06-25 10:29 ` Roger Pau Monné
2014-06-25 10:34 ` Roger Pau Monné
2014-06-25 10:37 ` 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=538475BF0200007800015ECC@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--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 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).