From: Sascha Hauer <s.hauer@pengutronix.de>
To: Florian Klink <flokli@flokli.de>
Cc: barebox@lists.infradead.org
Subject: Re: use /usr/bin/env bash shebang instead of /bin/bash
Date: Mon, 2 Dec 2019 09:57:32 +0100 [thread overview]
Message-ID: <20191202085732.glnpepfo236vaxrk@pengutronix.de> (raw)
In-Reply-To: <20191127231946.27941-1-flokli@flokli.de>
Hi FLorian,
On Thu, Nov 28, 2019 at 12:19:43AM +0100, Florian Klink wrote:
>
> Some distributions might not have bash in /bin, but in $PATH.
>
> Using #!/usr/bin/env bash solves this, and is consistent with how the
> perl and python shebangs look like in the tree.
What is the exact case you are fixing with these patches? I am fine with
merging them generally, I just want to understand why and where you need
it.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-12-02 8:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 23:19 Florian Klink
2019-11-27 23:19 ` [PATCH 1/3] scripts: use #!/usr/bin/env bash shebang instead of #!/bin/bash Florian Klink
2019-12-03 6:46 ` Michael Olbrich
2019-12-03 8:45 ` Sascha Hauer
2019-12-03 9:12 ` Michael Olbrich
2019-12-05 21:45 ` [PATCH v2 1/4] " Florian Klink
2019-12-05 21:45 ` [PATCH v2 2/4] dts/scripts: " Florian Klink
2019-12-05 21:45 ` [PATCH v2 3/4] docs: " Florian Klink
2019-12-05 21:45 ` [PATCH v2 4/4] docs: use #!/usr/bin/env python shebang instead of #!/usr/bin/python Florian Klink
2019-12-06 11:31 ` [PATCH v2 1/4] scripts: use #!/usr/bin/env bash shebang instead of #!/bin/bash Roland Hieber
2019-12-06 12:32 ` use #!/usr/bin/env binary instead of #!/usr/bin/binary Florian Klink
2019-12-06 12:32 ` [PATCH v3 1/4] scripts: use #!/usr/bin/env bash shebang instead of #!/bin/bash Florian Klink
2019-12-06 12:32 ` [PATCH v3 2/4] dts/scripts: " Florian Klink
2019-12-06 12:32 ` [PATCH v3 3/4] docs: " Florian Klink
2019-12-06 12:32 ` [PATCH v3 4/4] docs: use #!/usr/bin/env python shebang instead of #!/usr/bin/python Florian Klink
2019-12-06 14:25 ` use #!/usr/bin/env binary instead of #!/usr/bin/binary Sascha Hauer
2019-12-03 12:50 ` [PATCH 1/3] scripts: use #!/usr/bin/env bash shebang instead of #!/bin/bash Roland Hieber
2019-11-27 23:19 ` [PATCH 2/3] dts/scripts: " Florian Klink
2019-11-27 23:19 ` [PATCH 3/3] docs: " Florian Klink
2019-12-02 8:57 ` Sascha Hauer [this message]
2019-12-02 14:29 ` use /usr/bin/env bash shebang instead of /bin/bash Florian Klink
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=20191202085732.glnpepfo236vaxrk@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=flokli@flokli.de \
/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