From: Greg KH <greg@kroah.com>
To: Nicolas Schier <nicolas@fjasle.eu>
Cc: stable@vger.kernel.org, Finn Behrens <me@kloenk.de>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH v2 1/2] tweewide: Fix most Shebang lines
Date: Wed, 12 May 2021 13:58:17 +0200 [thread overview]
Message-ID: <YJvC2W9QTpc9JBp1@kroah.com> (raw)
In-Reply-To: <20210511185817.2695437-2-nicolas@fjasle.eu>
On Tue, May 11, 2021 at 08:58:16PM +0200, Nicolas Schier wrote:
> From: Finn Behrens <me@kloenk.de>
>
> commit c25ce589dca10d64dde139ae093abc258a32869c upstream.
>
> Change every shebang which does not need an argument to use /usr/bin/env.
> This is needed as not every distro has everything under /usr/bin,
> sometimes not even bash.
>
> Signed-off-by: Finn Behrens <me@kloenk.de>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> [nicolas@fjasle.eu: ported to v4.9, updated contexts, adapt for old
> scripts]
What about 4.14, 4.19, 5.4, and 5.10? We can't add patches only to one
stable tree and not all of the newer ones as well.
And what problem is this solving? What distro has problems with this
for this old kernel tree?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-12 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 18:58 [PATCH v2 0/2] shebang fixes and explicit python3 switch for v4.9 Nicolas Schier
2021-05-11 18:58 ` [PATCH v2 1/2] tweewide: Fix most Shebang lines Nicolas Schier
2021-05-12 11:58 ` Greg KH [this message]
2021-05-13 20:03 ` Nicolas Schier
2021-05-17 12:01 ` Greg KH
2021-05-11 18:58 ` [PATCH v2 2/2] scripts: switch explicitly to Python 3 Nicolas Schier
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=YJvC2W9QTpc9JBp1@kroah.com \
--to=greg@kroah.com \
--cc=masahiroy@kernel.org \
--cc=me@kloenk.de \
--cc=nicolas@fjasle.eu \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox