From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: keir@xen.org, xen-devel@lists.xensource.com,
"xen.org" <ian.jackson@eu.citrix.com>,
stefano.stabellini@eu.citrix.com
Subject: Re: [xen-unstable bisection] complete build-armhf
Date: Thu, 30 May 2013 21:55:01 +0100 [thread overview]
Message-ID: <1369947301.20923.18.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <51A7B52E.3040409@citrix.com>
On Thu, 2013-05-30 at 21:23 +0100, Julien Grall wrote:
> Hello,
>
> I'm sorry for this compilation breakage :/.
I somehow missed this in my build test as well :-/
> I have either an incremental fix:
Which I have applied, thanks.
Ian.
next prev parent reply other threads:[~2013-05-30 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 19:59 [xen-unstable bisection] complete build-armhf xen.org
2013-05-30 20:23 ` Julien Grall
2013-05-30 20:55 ` Ian Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-15 2:13 xen.org
2013-07-10 2:51 xen.org
2013-07-10 9:09 ` Julien Grall
2013-08-08 23:00 xen.org
2014-09-10 16:52 xen.org
2015-03-25 2:05 xen.org
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=1369947301.20923.18.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.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.