From: Christoph Egger <Christoph_Egger@gmx.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools: use PREFIX when building upstream qemu
Date: Thu, 10 Jan 2013 22:50:58 +0100 [thread overview]
Message-ID: <50EF37C2.2020507@gmx.de> (raw)
In-Reply-To: <20681.61235.10341.776924@mariner.uk.xensource.com>
On 13.12.12 16:07, Ian Jackson wrote:
> Christoph Egger writes ("Re: [Xen-devel] [PATCH] tools: use PREFIX when building upstream qemu"):
>> Yes, this is right.
>>
>> It is also routinely exposed when you choose a different prefix
>> for different xen versions for development purpose.
>> I use xen-<c/s> to switch forth and back between different
>> xen versions. This way I am always able to use a working version
>> and to test a new changeset.
>
> Right. So we'd appreciate your opinion :-).
My opinion is: Use PREFIX for default
and use --docdir, --mandir, --bindir, etc.
to specify the other stuff so that everything
goes where it belongs to.
Christoph
next prev parent reply other threads:[~2013-01-10 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 10:38 [PATCH] tools: use PREFIX when building upstream qemu Christoph Egger
2012-10-25 12:39 ` Ian Jackson
2012-10-26 9:47 ` Christoph Egger
2012-10-26 10:15 ` Ian Campbell
2012-10-26 11:09 ` Christoph Egger
2012-12-13 10:40 ` Ian Campbell
2012-12-13 14:22 ` Christoph Egger
2012-12-13 14:25 ` Ian Jackson
2012-12-13 14:41 ` Christoph Egger
2012-12-13 15:07 ` Ian Jackson
2013-01-10 21:50 ` Christoph Egger [this message]
2012-12-13 14:28 ` Ian Campbell
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=50EF37C2.2020507@gmx.de \
--to=christoph_egger@gmx.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.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.