From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Keir (Xen.org)" <keir@xen.org>, "Tim (Xen.org)" <tim@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [xen-unstable test] 17914: tolerable FAIL
Date: Wed, 8 May 2013 09:55:18 +0100 [thread overview]
Message-ID: <518A12F6.4090000@eu.citrix.com> (raw)
In-Reply-To: <518A10FB02000078000D435C@nat28.tlf.novell.com>
On 08/05/13 07:46, Jan Beulich wrote:
>>>> On 07.05.13 at 18:43, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
>> Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 17914: tolerable FAIL"):
>>> Ian, I see you also tagged the Xen tree, but unfortunately without
>>> updating the hypervisor revision to -rc1? Was that intentional? It's
>>> not a dramatic problem (and I don't see a need to withdraw and
>>> redo the tag), but maybe worth an addition to the checklist.
>> You mean XEN_EXTRAVERSION in xen/Makefile ? I wasn't sure
>> whether that ought to be changed. It's on the checklist but I don't
>> know what the usual practice is for an RC.
> Keir updated that in the past for the RCs, but personally I don't
> mind it remaining "-unstable" until the branching occurs.
I think it would be better to update the EXTRAVERSION, but it's not a
terribly big deal I don't think.
-George
prev parent reply other threads:[~2013-05-08 8:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 8:27 [xen-unstable test] 17914: tolerable FAIL xen.org
2013-05-07 9:06 ` George Dunlap
2013-05-07 10:43 ` Ian Jackson
2013-05-07 10:55 ` Ian Campbell
2013-05-07 12:42 ` [PATCH] README: update version number Ian Jackson
2013-05-07 12:43 ` George Dunlap
2013-05-07 12:59 ` Ian Campbell
2013-05-07 13:00 ` George Dunlap
2013-05-07 13:03 ` Ian Jackson
2013-05-07 12:45 ` Ian Campbell
2013-05-07 19:06 ` Keir Fraser
2013-05-07 11:13 ` [xen-unstable test] 17914: tolerable FAIL Stefano Stabellini
2013-05-07 14:12 ` Jan Beulich
2013-05-07 14:16 ` George Dunlap
2013-05-07 14:20 ` Jan Beulich
2013-05-07 14:21 ` George Dunlap
2013-05-07 16:43 ` Ian Jackson
2013-05-08 6:46 ` Jan Beulich
2013-05-08 8:33 ` Ian Campbell
2013-05-08 8:52 ` George Dunlap
2013-05-08 9:02 ` Jan Beulich
2013-05-08 8:55 ` George Dunlap [this message]
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=518A12F6.4090000@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.