From: Thorsten Glaser <tglaser@b1-systems.de>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: git hard-codes use of /bin/sh for aliases
Date: Tue, 12 May 2026 00:46:04 +0200 (CEST) [thread overview]
Message-ID: <9f279637-c0fe-c88b-24de-3a00b957ae3b@b1-systems.de> (raw)
In-Reply-To: <agJaS0xuMaLm6UZv@fruit.crustytoothpaste.net>
On Mon, 11 May 2026, brian m. carlson wrote:
>On Linux, I have mksh, but my work machine on macOS does not, so
>specifying `core.sh = /bin/mksh` would not work on all my systems. If
But it could be made possible by pointing it to ~/.etc/bin/mksh
on the Macintosh…
>I'll also note that Git doesn't handle aliases specially. Git has a
>with-shell and a without-shell mode for running commands, and we use the
>former for aliases.
Ah, okay.
I was merely wondering that it was not configurable for aliases.
When looking at the aliases in detail, I found that I already invoked
mksh -c '…' in those that used mksh-specific code, and that the one
that failed merely uses a recent POSIX sh construct that /bin/sh on
a customer system does not yet implement and I could reword it.
bye,
//Thorsten
--
Thorsten Glaser
Linux / Unix Developer
Tel.: +49 160 91168501
E-Mail: tglaser@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / https://www.b1-systems.de/
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537
prev parent reply other threads:[~2026-05-11 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 21:13 git hard-codes use of /bin/sh for aliases Thorsten Glaser
2026-05-11 22:38 ` brian m. carlson
2026-05-11 22:46 ` Thorsten Glaser [this message]
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=9f279637-c0fe-c88b-24de-3a00b957ae3b@b1-systems.de \
--to=tglaser@b1-systems.de \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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