From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Update QEMU_UPSTREAM_REVISION
Date: Mon, 2 Dec 2013 11:30:06 +0000 [thread overview]
Message-ID: <529C6F3E.2090904@eu.citrix.com> (raw)
In-Reply-To: <1385722374.25763.14.camel@kazak.uk.xensource.com>
On 11/29/2013 10:52 AM, Ian Campbell wrote:
> On Thu, 2013-11-28 at 19:44 +0000, Anthony PERARD wrote:
>> Changing to master, otherwise we don't get the last updates.
>>
>> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>
> WRT the release this patch is equivalent to "we should move to qemu
> 1.6". Did that get an exception already / is it on the list?
>
> (please don't forget to CC George at this stage in the release for his
> Ack, or to reference an existing release ack he gave)
Actually, isn't this "Fix incorrect assignment of a specific revision
instead of most-recently-passed for development branch"? It's the push
into the qemu tree that would require a release ack, but that happened a
month ago before the code freeze IIRC.
-George
next prev parent reply other threads:[~2013-12-02 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 17:02 [PATCH] Update QEMU_UPSTREAM_REVISION Anthony PERARD
2013-11-27 17:17 ` Ian Jackson
2013-11-27 17:31 ` Ian Campbell
2013-11-28 19:44 ` Anthony PERARD
2013-11-29 10:52 ` Ian Campbell
2013-12-02 11:30 ` George Dunlap [this message]
2013-12-02 11:40 ` Ian Campbell
2013-12-02 12:34 ` Ian Jackson
2013-12-04 14:53 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2013-12-19 16:34 Ian Jackson
2014-01-28 15:23 Stefano Stabellini
2014-01-28 15:26 ` George Dunlap
2014-01-28 16:05 ` Konrad Rzeszutek Wilk
2014-01-28 16:09 ` Stefano Stabellini
2014-01-28 16:17 ` Konrad Rzeszutek Wilk
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=529C6F3E.2090904@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.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.