From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH 0/2] Test fixes when running with zsh in sh mode
Date: Sat, 27 Apr 2024 10:23:19 -0700 [thread overview]
Message-ID: <xmqqil0267p4.fsf@gitster.g> (raw)
In-Reply-To: <20240426221154.2194139-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Fri, 26 Apr 2024 22:11:52 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> This series fixes two test failures with zsh when run in sh mode; that
> is, the mode that occurs when the shell is invoked as "sh". sh mode
> provides the most POSIX-compliant behavior and avoids a lot of
> incompatibilities that the default zsh mode provides.
Thanks, will queue.
prev parent reply other threads:[~2024-04-27 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 22:11 [PATCH 0/2] Test fixes when running with zsh in sh mode brian m. carlson
2024-04-26 22:11 ` [PATCH 1/2] t4046: avoid continue in &&-chain for zsh brian m. carlson
2024-04-26 22:11 ` [PATCH 2/2] vimdiff: make script and tests work with zsh brian m. carlson
2024-04-27 17:23 ` Junio C Hamano [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=xmqqil0267p4.fsf@gitster.g \
--to=gitster@pobox.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).