From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'brian m. carlson'" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>
Subject: RE: Report of use of "local" per t0000-basic.sh
Date: Mon, 25 Nov 2019 10:41:33 -0500 [thread overview]
Message-ID: <000d01d5a3a6$d454e610$7cfeb230$@nexbridge.com> (raw)
In-Reply-To: <20191123041616.GD6430@camp.crustytoothpaste.net>
On November 22, 2019 11:16 PM, brian m. carlson wrote:
> Is there some place in particular that you've found we're using it outside of a
> function? I don't know about others, but I'm certainly interested in fixing
> these. It looks like we do use it in a function in
> t0000 itself, though.
I have been checking more deeply into this. The "local" keyword is being interpreted as a program instead of a keyword on the default shell on z/OS V2R3 USS even in functions. There are two shells, something resembling ksh and another tcsh. Tests do not run at all in tcsh (no support for . file). The ksh does not implement "local", so no option there. There is a bash port available, which supports local, but subtest 43 (tests clean up even on failures) does not work, although subtest 1 does work. To make any of this work, I have had to modify the tests to explicitly tag created files as ISO8859-1 (touch file && chtag -c ISO8859-1) because by default IBM-1047 is used (filesystem configured default), and test_cmp simply does not like IBM-1047 format.
prev parent reply other threads:[~2019-11-25 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 19:04 Report of use of "local" per t0000-basic.sh Randall S. Becker
2019-11-23 4:16 ` brian m. carlson
2019-11-24 4:24 ` Junio C Hamano
2019-11-25 15:41 ` Randall S. Becker [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='000d01d5a3a6$d454e610$7cfeb230$@nexbridge.com' \
--to=rsbecker@nexbridge.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 NNTP newsgroup(s).