All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Alecs King <alecsk@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] #!/bin/sh --> #!/usr/bin/env bash
Date: Fri, 22 Apr 2005 22:34:12 -0400	[thread overview]
Message-ID: <4269B424.8010406@dwheeler.com> (raw)
In-Reply-To: <4268A9C5.5090102@zytor.com>


> Alecs King wrote:
> 
>>
>> And as for bash, only gitdiff-do and gitlog.sh 'explicitly' use bash
>> instead of /bin/sh.  On most Linux distros, /bin/sh is just a symbolic
>> link to bash.  But not on some others.  I found gitlsobj.sh could not
>> work using a plain /bin/sh on fbsd.  To make life easier, i think it
>> might be better if we all explicitly use bash for all shell scripts.


H. Peter Anvin wrote:
> How about #!/bin/bash (build from .in files if you feel it necessary to 
> support systems which don't have bash in /bin) instead of doubling the 
> number of execs?

If # of execs is that critical, it probably should not be in
bash anyway.  OpenBSD (at least 3.1)'s bash appears to be in
/usr/local/bin/bash, NOT /bin/bash.
I'd go with the /bin/env solution for now;
it maximizes the "it just works" factor, and
when it comes time for .in files much of the cogito code (at least)
will probably be rewritten in Perl, and anything performance-sensitive
will be in C.

--- David A. Wheeler

  reply	other threads:[~2005-04-23  2:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21  5:06 Performance of various compressors Mike Taht
2005-04-21  5:14 ` Mike Taht
2005-04-21  5:22   ` [PATCH] experimental - " Mike Taht
2005-04-21 10:23     ` HOWTO: PATCH: don't hardcode path-to-bash, use sys/limits.h Klaus Robert Suetterlin
2005-04-21 14:31       ` Alecs King
2005-04-21 19:42         ` [PATCH] #!/bin/sh --> #!/usr/bin/env bash Alecs King
2005-04-22  7:37           ` H. Peter Anvin
2005-04-23  2:34             ` David A. Wheeler [this message]
2005-04-23  6:16               ` H. Peter Anvin
2005-04-22 20:38 ` Performance of various compressors Aaron Lehmann
2005-04-25 12:17   ` git I/O performance (was: Performance of various compressors) Klaus Robert Suetterlin

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=4269B424.8010406@dwheeler.com \
    --to=dwheeler@dwheeler.com \
    --cc=alecsk@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.