From: Olaf Hering <olaf@aepfle•de>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, stable@kernel•org,
Sean MacLennan <smaclennan@pikatech•com>
Subject: Re: [PATCH] [powerpc] do not expect executable permissions for in-tree shell scripts
Date: Thu, 10 Jun 2010 17:20:40 +0200 [thread overview]
Message-ID: <20100610152040.GA30274@aepfle.de> (raw)
In-Reply-To: <1276151189.1962.47.camel@pasglop>
On Thu, Jun 10, Benjamin Herrenschmidt wrote:
> I still don't like it very much.. why not chmod'ing it +x instead ? :-)
I looked at a few other scripts in the source tree, they are called with
$(CONFIG_SHELL) <name>, or perl <name>, or awk <name> or even sh <name>.
So my change adds some sort of consistency and makes packaging more robust.
Olaf
prev parent reply other threads:[~2010-06-10 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 8:10 [PATCH] [powerpc] do not expect executable permissions for in-tree shell scripts Olaf Hering
2010-06-05 17:32 ` Sean MacLennan
2010-06-05 17:44 ` Olaf Hering
2010-06-05 18:00 ` Sean MacLennan
2010-06-10 6:26 ` Benjamin Herrenschmidt
2010-06-10 15:20 ` Olaf Hering [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=20100610152040.GA30274@aepfle.de \
--to=olaf@aepfle$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=smaclennan@pikatech$(echo .)com \
--cc=stable@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox