From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Whit Armstrong <armstrong.whit@gmail.com>,
Asheesh Laroia <asheesh@asheesh.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Solaris test failure for git-1.5.4.4 -- t0021-conversion.sh
Date: Tue, 11 Mar 2008 21:11:28 -0700 [thread overview]
Message-ID: <7vhcfc8tu7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080311174045.GB14687@sigill.intra.peff.net
Jeff King <peff@peff.net> writes:
>> Looks like /usr/ucb/tr is OK with this, but /usr/bin/tr is not. Both
>> seem to handle the more verbose:
>>
>> tr \
>> 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ' \
>> 'nopqrstuvwxyzabcdefghijklmNOPQRSTUVWXYZABCDEFGHIJKLM'
Besides tests, I think we have invocations of "tr" that Solaris people
might want to audit in the real scripts. POSIX does not require [] around
the strings, but when from-string and to-string are of the same length,
having [] around them would not hurt (they transliterate to themselves)
and that is the only reason why we tend to use [] form to help potential
porters to ancient System V systems ;-)
filter-branch uses A-Z (BSD style) range which also is Kosher in POSIX but
will break historical System V that requires [] around ranges.
bisect has "tr '[\012]' ' '" which I think we can get rid of by rewriting
the users of the resulting string.
next prev parent reply other threads:[~2008-03-12 4:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 12:33 Solaris test failure for git-1.5.4.4 -- t0021-conversion.sh Whit Armstrong
2008-03-11 12:52 ` Johannes Schindelin
2008-03-11 17:17 ` Johannes Sixt
2008-03-11 17:35 ` David Kastrup
2008-03-11 16:55 ` Asheesh Laroia
2008-03-11 17:14 ` Whit Armstrong
2008-03-11 17:35 ` Jeff King
2008-03-11 17:40 ` Jeff King
2008-03-11 17:58 ` Whit Armstrong
2008-03-12 4:11 ` Junio C Hamano [this message]
2008-03-12 12:43 ` Jeff King
2008-03-12 12:48 ` Jeff King
2008-03-12 13:11 ` Johannes Schindelin
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=7vhcfc8tu7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=armstrong.whit@gmail.com \
--cc=asheesh@asheesh.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).