(off-list ancestor, not in this archive)
Re: [PATCH]: git-merge-one-file-script use /usr/bin/env to call bash · Junio C Hamano <hidden> · 2016-06-15
[PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · Thomas Glanzmann <hidden> · 2016-06-15
Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · bert hubert <hidden> · 2016-06-15
Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · Thomas Glanzmann <hidden> · 2016-06-15
Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · Martin Waitz <hidden> · 2016-06-15
Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · Morten Welinder <hidden> · 2016-06-15
Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · Thomas Glanzmann <hidden> · 2016-06-15
Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility · "H. Peter Anvin" <hpa@zytor.com> · 2016-06-15

Re: [PATCH] Use backticks instead of $(command) to maintain /bin/sh compatibility

From: Morten Welinder <hidden>
Date: 2016-06-15 22:41:56

On 5/7/05, Martin Waitz [off-list ref] wrote:

hoi :)

On Sat, May 07, 2005 at 11:05:43AM +0200, Thomas Glanzmann wrote:

quoted

* Junio C Hamano [off-list ref] [050507 10:54]:

quoted

A quick question.  Which construct in this bashism?
Not using backtick but saying $(command)?

Exactly:

huh? which broken shell does not understand $()?

Solaris' /bin/sh

I thought everything we were relying on bash anyway.  It'll take it.

Morten