From: Paolo Bonzini <pbonzini@redhat.com>
To: "Joel Granados" <joel.granados@kernel.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] scripts: nixify archive-source.sh
Date: Thu, 10 Apr 2025 14:18:01 +0200 [thread overview]
Message-ID: <4f64f6a8-2e4a-4e20-b2c8-8f87b8b7900c@redhat.com> (raw)
In-Reply-To: <20250408-jag-sysctl-v1-1-3f4f38b751be@kernel.org>
On 4/8/25 22:14, Joel Granados wrote:
> Use "#!/usr/bin/env bash" instead of "#!/bin/bash". This is necessary
> for nix environments as they only provide /usr/bin/env at the standard
> location.
I am confused, how does this not break everything else? All the test
scripts in tests/docker/test-* have "#!/bin/bash", and configure has
"/bin/sh". How is the environment that runs scripts/archive-source.sh
different, and why should it be fixed in scripts/archive-source.sh?
These are genuine questions - it would help if the commit message
explained those... In fact, what is a nix overlay and why would you use
scripts/archive-source.sh to prepare one? :)
>
> Signed-off-by: Joel Granados <joel.granados@kernel.org>
> ---
> scripts/archive-source.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/archive-source.sh b/scripts/archive-source.sh
> index 30677c3ec9032ea01090f74602d839d1c571d012..a469a5e2dec4b05e51474f0a1af190c1ccf23c7e 100755
> --- a/scripts/archive-source.sh
> +++ b/scripts/archive-source.sh
> @@ -1,4 +1,4 @@
> -#!/bin/bash
> +#!/usr/bin/env bash
> #
> # Author: Fam Zheng <famz@redhat.com>
> #
>
next prev parent reply other threads:[~2025-04-10 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 20:14 [PATCH 0/3] scripts: Add a root dir in archve-source.sh Joel Granados
2025-04-08 20:14 ` [PATCH 1/3] scripts: nixify archive-source.sh Joel Granados
2025-04-09 9:41 ` Thomas Huth
2025-04-10 12:18 ` Paolo Bonzini [this message]
2025-04-28 19:02 ` Joel Granados
2025-04-08 20:14 ` [PATCH 2/3] scripts: Add root dir to arguments Joel Granados
2025-04-08 20:14 ` [PATCH 3/3] scripts: Clarify doc messages in archive-source.sh Joel Granados
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=4f64f6a8-2e4a-4e20-b2c8-8f87b8b7900c@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=joel.granados@kernel.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).