From: Christoph Egger <chegger@amazon.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Matt Wilson <msw@amazon.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Make sure to use tools as found by configure
Date: Mon, 13 May 2013 12:59:18 +0200 [thread overview]
Message-ID: <5190C786.4050505@amazon.de> (raw)
In-Reply-To: <1368438711.537.21.camel@zakaz.uk.xensource.com>
On 13.05.13 11:51, Ian Campbell wrote:
> On Fri, 2013-05-10 at 18:10 +0100, Matt Wilson wrote:
>> On Fri, May 10, 2013 at 01:59:53PM +0200, Christoph Egger wrote:
>>>
>>> Hi,
>>>
>>> attached patch makes the build process work as described at
>>> http://wiki.xen.org/wiki/Compiling_Xen_From_Source_on_NetBSD
>>>
>>> Without this patch compiling the xen kernel fails with
>>> python: No such file or directory
>>>
>>> Note, this patch enforces to run configure before you
>>> can compile the xen kernel.
>>> This is already required to build tools and stubdom anyway.
>>>
>>> This makes an other patch work as submitted:
>>> http://lists.xen.org/archives/html/xen-devel/2013-04/msg02098.html
>>>
>>> Christoph
>>>
>>>
>>> commit 7172e6e0020328d14638a0bbb66a52c905cb4b0b
>>> Author: Christoph Egger <chegger@amazon.de>
>>> Date: Thu Feb 7 14:29:19 2013 +0000
>>>
>>> Make sure to use tools as found by configure.
>>> Fold inclusion of Tools.mk into toplevel Config.mk.
>>>
>>> Signed-off-by: Christoph Egger <chegger@amazon.de>
>>> Reviewed-by: Matthew Wilson <msw@amazon.com>
>>
>> To be clear, I Nack'ed this in review and gave two options:
>
> I was about to query this, thanks for clarifying.
>
> Christoph, please be more careful in future not to misrepresent peoples
> review.
>
> In general I would think it a good idea if Reviewed-by tags are posted
> publicly by the Reviewer on xen-devel, even if the review was carried
> out internally prior to posting, this would help avoid this sort of
> issue. Not a rule I don't think, but would help avoid mistakes...
Understood.
Christoph
next prev parent reply other threads:[~2013-05-13 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 11:59 [PATCH] Make sure to use tools as found by configure Christoph Egger
2013-05-10 12:14 ` Ian Campbell
2013-05-10 12:49 ` Tim Deegan
2013-05-10 17:06 ` Matt Wilson
2013-05-10 17:10 ` Matt Wilson
2013-05-13 9:51 ` Ian Campbell
2013-05-13 10:59 ` Christoph Egger [this message]
2013-05-13 20:32 ` Matt Wilson
2013-05-14 8:44 ` Ian Campbell
2013-05-14 9:09 ` Christoph Egger
2013-05-16 8:30 ` Matt Wilson
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=5190C786.4050505@amazon.de \
--to=chegger@amazon.de \
--cc=Ian.Campbell@citrix.com \
--cc=msw@amazon.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.