From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: "mike.dickson@hp.com" <mike.dickson@hp.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: XenClient builds
Date: Tue, 03 Mar 2009 22:27:12 +0000 [thread overview]
Message-ID: <49ADAEC0.9090106@eu.citrix.com> (raw)
In-Reply-To: <1236115551.20671.14.camel@localhost.localdomain>
Mike Dickson wrote:
> I've pulled a build tree from the git repository for XenClient as
> mentioned in Ian's talk last week at the summit. A number of the
> configurations don't build cleanly. Before I start firing away is the
> xen-devel list the appropriate place to discuss XenClient or is another
> list being used?
I think it's fine for now until we got a more appropriate place.
> Is there a lead for the project that might take
> questions about should be expected to work and what needs attention?
Well, Ian is the project lead, but I'll be happy to answer as many
questions as I can too. also if you know about anything that doesn't
build out of the box, please let me know.
--
Vincent
prev parent reply other threads:[~2009-03-03 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 21:25 XenClient builds Mike Dickson
2009-03-03 22:27 ` Vincent Hanquez [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=49ADAEC0.9090106@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=mike.dickson@hp.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.