All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Shriram Rajagopalan <rshriram@gmail.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
	Carsten Schiers <carsten@schiers.de>,
	Fabio Fantoni <fabio.fantoni@heliman.it>
Subject: Re: Re: Xen 4.1.2 - when ?
Date: Sat, 27 Aug 2011 10:27:59 +0100	[thread overview]
Message-ID: <CA7E772F.1FD9C%keir.xen@gmail.com> (raw)
In-Reply-To: <CAP8mzPP0oUmbfBMWuWW7c98QP_Ji41yZvVd9E-jKBssepYWYKg@mail.gmail.com>

On 27/08/2011 10:10, "Shriram Rajagopalan" <rshriram@gmail.com> wrote:

> On Thu, Aug 25, 2011 at 11:06 AM, Ian Jackson <Ian.Jackson@eu.citrix.com>
> wrote:
>> (xen-devel added to the CC)
>> 
>> Carsten Schiers writes ("AW: [Xen-devel] Re: Xen 4.1.2 - when ?"):
>>> Hi Keir, did you intentionally left these out for 4.1.2?
>>> 
>>> They improve usability of xl toolstack as xend replacement.
>>> 
>>> http://xenbits.xen.org/hg/xen-unstable.hg/rev/0648846b4d17
>>> http://xenbits.xen.org/hg/xen-unstable.hg/rev/2ae357405850
>>> http://xenbits.xen.org/hg/xen-unstable.hg/rev/c2995f0555af
>> 
>> I'm happy with all of these being backported.
>> 
>> The first two apply cleanly to 4.1-testing.  Keir, should I port them
>> across or do you have a clever backport script ?
>>   
>> The last one, c2995f0555af, has conflicts.  Carsten, would you care to
>> post a version against 4.1 ?
>> 
>> Thanks,
>> Ian.
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> Keir,
>  I would like to backport the following fixes and patches related to Remus.
> 
> 1. http://xenbits.xen.org/hg/xen-unstable.hg/rev/c8ae80a11d47
> 2. http://xenbits.xen.org/hg/xen-unstable.hg/rev/29d81623dc14
> 3. http://xenbits.xen.org/hg/xen-unstable.hg/rev/b04e57ec4671
> 4. http://xenbits.xen.org/hg/xen-unstable.hg/rev/62c0dfc9efbf
> 5. http://xenbits.xen.org/hg/xen-unstable.hg/rev/ecff559bf474
> 6. http://xenbits.xen.org/hg/xen-unstable.hg/rev/15fc211a13bf
> 
> Patches 2-6 apply cleanly against 4.1-testing. Patch 1 does not apply cleanly
> as it has some content that I didn't post, but seems to have gotten in while
> IanJ was committing it (something related to
> tools/python/xen/xm/messages/xen-xm.pot).

I'll leave it to Ian Jackson to backport these if he agrees with your
choices.

 -- Keir

> shriram
> 
> 

  parent reply	other threads:[~2011-08-27  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17168217.131314282259003.JavaMail.root@uhura>
2011-08-25 15:06 ` AW: Re: Xen 4.1.2 - when ? Ian Jackson
     [not found]   ` <CAP8mzPP0oUmbfBMWuWW7c98QP_Ji41yZvVd9E-jKBssepYWYKg@mail.gmail.com>
2011-08-27  9:19     ` Shriram Rajagopalan
2011-08-27  9:27     ` Keir Fraser [this message]
2011-08-30 16:59     ` Ian Jackson
2011-08-16 13:26 Jan Beulich
2011-08-16 14:12 ` Keir Fraser
2011-08-16 18:16   ` Stefano Stabellini
  -- strict thread matches above, loose matches on Subject: below --
2011-08-12 16:03 Jan Beulich
2011-08-12 16:18 ` Keir Fraser
2011-08-15  6:22   ` Jan Beulich
2011-08-12 15:51 Keir Fraser
2011-08-12 16:20 ` Andrew Cooper
2011-08-12 17:02   ` 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=CA7E772F.1FD9C%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=carsten@schiers.de \
    --cc=fabio.fantoni@heliman.it \
    --cc=rshriram@gmail.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.