From: Peter Xu <peterx@redhat.com>
To: Sergey Bronnikov <sergeyb@bronevichok.ru>
Cc: kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] Use /bin/env in shebang to make scripts more portable
Date: Wed, 15 Mar 2017 18:48:00 +0800 [thread overview]
Message-ID: <20170315104800.GG5971@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170315102550.GA44201@Sergeys-MacBook-Pro-2.local>
On Wed, Mar 15, 2017 at 01:25:50PM +0300, Sergey Bronnikov wrote:
> Some operating systems installs bash executable file to other directory
> than /bin. So it is better to use env utility to find bash.
Signed-off line missing. Besides that:
Reviewed-by: Peter Xu <peterx@redhat.com>
-- peterx
next prev parent reply other threads:[~2017-03-15 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 10:25 [kvm-unit-tests PATCH] Use /bin/env in shebang to make scripts more portable Sergey Bronnikov
2017-03-15 10:48 ` Peter Xu [this message]
2017-03-15 12:31 ` Sergey Bronnikov
2017-03-16 7:38 ` Thomas Huth
2017-03-17 5:11 ` Sergey Bronnikov
2017-03-17 8:04 ` Thomas Huth
2017-03-17 11:11 ` Sergey Bronnikov
2017-03-17 11:18 ` Paolo Bonzini
2017-03-17 12:28 ` Thomas Huth
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 11:12 Sergey Bronnikov
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=20170315104800.GG5971@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=sergeyb@bronevichok.ru \
/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