From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Billes Tibor <tbilles@gmx.com>
Subject: Re: [PATCH v2 0/1] Run pipeline command in subshell in sh mode
Date: Sat, 6 Jun 2020 00:31:34 +0000 [thread overview]
Message-ID: <20200606003134.GH6569@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20200606002241.1578150-2-sandals@crustytoothpaste.net>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On 2020-06-06 at 00:22:40, brian m. carlson wrote:
> POSIX sh implementations run each command in a pipeline in a subshell,
> although zsh (and AT&T ksh) do not: instead, they run the final command
> in the main shell. This leads to very different behavior when the final
> command is a shell function which modifies variables.
Sorry about this and the following patch. I forgot to clean my patches
directory before sending, and accidentally sent some patches for zsh.
My apologies.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-06-06 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 5:15 git-fast-import out of memory Billes Tibor
2020-06-05 22:43 ` brian m. carlson
2020-06-06 0:22 ` [PATCH] fast-import: fix incomplete conversion with multiple mark files brian m. carlson
2020-06-06 0:22 ` [PATCH v2 0/1] Run pipeline command in subshell in sh mode brian m. carlson
2020-06-06 0:31 ` brian m. carlson [this message]
2020-06-06 0:22 ` [PATCH v2] exec: run final pipeline command in a " brian m. carlson
2020-06-08 15:52 ` [PATCH] fast-import: fix incomplete conversion with multiple mark files Tibor Billes
2020-06-08 16:47 ` Junio C Hamano
2020-06-08 22:58 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200606003134.GH6569@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tbilles@gmx.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).