From: "Sean" <seanlkml@sympatico.ca>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Peter Eriksen" <s022018@student.dtu.dk>, git@vger.kernel.org
Subject: Re: /bin/sh portability question
Date: Fri, 23 Sep 2005 05:02:57 -0400 (EDT) [thread overview]
Message-ID: <BAYC1-PASMTP05141C92C0F083A17B2EEFAE960@CEZ.ICE> (raw)
Message-ID: <54643.10.10.10.28.1127466177.squirrel@linux1> (raw)
In-Reply-To: <7vzmq4faz6.fsf@assigned-by-dhcp.cox.net>
On Fri, September 23, 2005 4:24 am, Junio C Hamano said:
> I haven't assessed the extent of damage if we tried to use ``
> for portability lately (I did once, and it did not look too bad
> back then). If somebody comes up with a readable patch, I might
> be persuaded to take it [*1*].
Junio,
It sounds like changing the sha-bang line to "#!/bin/bash" would fix the
problem on Solaris. As an aside, it would improve vi syntax highlighting
as well. Does any target system lack bash?
If not, would you accept a patch that first converted the shell scripts to
#!/bin/bash and then added a "make install" option that allowed them to be
replaced? Something like "make install S=/bin/ash" for instance?
Sean
next prev parent reply other threads:[~2005-09-23 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 7:50 /bin/sh portability question Peter Eriksen
2005-09-23 8:24 ` Junio C Hamano
[not found] ` <54643.10.10.10.28.1127466177.squirrel@linux1>
2005-09-23 9:02 ` Sean [this message]
2005-09-23 9:19 ` Junio C Hamano
[not found] ` <39450.10.10.10.28.1127471685.squirrel@linux1>
2005-09-23 10:34 ` Sean
2005-09-25 19:26 ` Nico -telmich- Schottelius
[not found] ` <33541.10.10.10.28.1127677005.squirrel@linux1>
2005-09-25 19:36 ` Sean
2005-09-23 9:07 ` Junio C Hamano
2005-09-23 12:17 ` Peter Eriksen
2005-09-24 1:13 ` Junio C Hamano
[not found] ` <20050924195029.GA20514@bohr.gbar.dtu.dk>
2005-09-24 21:31 ` Junio C Hamano
2005-09-24 17:35 ` Patrick Mauritz
2005-09-23 19:48 ` H. Peter Anvin
2005-09-23 19:55 ` Morten Welinder
2005-09-23 19:57 ` Joel Becker
2005-09-23 20:00 ` H. Peter Anvin
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=BAYC1-PASMTP05141C92C0F083A17B2EEFAE960@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=s022018@student.dtu.dk \
/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).