From: Bryan O'Sullivan <bos@serpentine.com>
To: Steven Hand <steven.hand@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, steven@xensource.com
Subject: Re: [PATCH] [build] Fix xen-unstable build
Date: Fri, 22 Sep 2006 15:42:20 -0700 [thread overview]
Message-ID: <1158964940.32666.10.camel@chalcedony.pathscale.com> (raw)
In-Reply-To: <097d01c6de96$75e8a780$80cda8c0@Violet>
On Fri, 2006-09-22 at 23:28 +0100, Steven Hand wrote:
> > This patch is needed for a current xen-unstable build to complete. This
> > file appears to have been broken for almost two months.
>
> Obviously not been broken for us - what compiler / distro are you using?
> What arch?
FC6t3, i386. I literally just ran "make" in a clean repo, didn't diddle
anything.
<b
next prev parent reply other threads:[~2006-09-22 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 16:53 [PATCH] [build] Fix xen-unstable build Bryan O'Sullivan
2006-09-22 22:28 ` Steven Hand
2006-09-22 22:42 ` Bryan O'Sullivan [this message]
2006-09-22 22:52 ` Ian Pratt
2006-09-22 23:43 ` Bryan O'Sullivan
2006-09-22 22:50 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 22:46 Steven Hand
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=1158964940.32666.10.camel@chalcedony.pathscale.com \
--to=bos@serpentine.com \
--cc=steven.hand@cl.cam.ac.uk \
--cc=steven@xensource.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.