From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] tools/check: check for yajl (needed by libxl)
Date: Fri, 30 Sep 2011 14:15:42 +0200 [thread overview]
Message-ID: <20110930121542.GA25896@aepfle.de> (raw)
In-Reply-To: <1317384428.26672.269.camel@zakaz.uk.xensource.com>
On Fri, Sep 30, Ian Campbell wrote:
> On Fri, 2011-09-30 at 13:02 +0100, Olaf Hering wrote:
> > On Fri, Sep 30, Ian Campbell wrote:
> >
> > > (note to committer, ensure the new file is executable)
> >
> > Please dont, thats not patch friendly.
> >
> > Shouldnt all script files be called with like
> > '$interpreter $script' instead of './$script'?
>
> In general I agree, but that isn't how it the infrastructure in
> tools/check/chk works right now.
There is tools/check/check_logging, which says it requires code with is
included in Python 2.3 and later.
The toplevel README states 2.3 or later is required, so
tools/check/check_logging could be removed and line 63 in
tools/check/chk be updated.
Olaf
next prev parent reply other threads:[~2011-09-30 12:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 7:36 [PATCH] tools/check: check for yajl (needed by libxl) Ian Campbell
2011-09-30 10:35 ` Anthony PERARD
2011-09-30 10:39 ` Ian Campbell
2011-10-04 14:48 ` Andre Przywara
2011-10-04 15:00 ` Ian Campbell
2011-10-05 8:24 ` Andre Przywara
2011-10-05 9:35 ` Ian Campbell
2011-10-05 11:57 ` Olaf Hering
2011-09-30 12:02 ` Olaf Hering
2011-09-30 12:07 ` Ian Campbell
2011-09-30 12:15 ` Olaf Hering [this message]
2011-09-30 12:20 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2011-10-05 9:42 Ian Campbell
2011-10-10 15:50 ` Ian Jackson
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=20110930121542.GA25896@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@eu.citrix.com \
--cc=anthony.perard@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.