From: Eric Sunshine <sunshine@sunshineco.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Git List" <git@vger.kernel.org>, "Jeff King" <peff@peff.net>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH v3 05/11] t0027: make hash size independent
Date: Fri, 31 Aug 2018 14:40:12 -0400 [thread overview]
Message-ID: <CAPig+cSSs9a_RSnc6==zb70Swh1L1Ok4y-DGc8YawPyea0Gm9Q@mail.gmail.com> (raw)
In-Reply-To: <20180831182141.GA9399@tor.lan>
On Fri, Aug 31, 2018 at 2:21 PM Torsten Bögershausen <tboegi@web.de> wrote:
> > diff --git a/t/t0027-auto-crlf.sh b/t/t0027-auto-crlf.sh
> > @@ -14,11 +14,13 @@ compare_files () {
> > compare_ws_file () {
> > + tmp=$2.tmp
> > act=$pfx.actual.$3
> > - tr '\015\000abcdef0123456789' QN00000000000000000 <"$2" >"$exp" &&
> > + tr '\015\000abcdef0123456789' QN00000000000000000 <"$2" >"$tmp" &&
> > tr '\015\000abcdef0123456789' QN00000000000000000 <"$3" >"$act" &&
> > + sed -e "s/0000*/$ZERO_OID/" "$tmp" >"$exp" &&
>
> Out of interest: why do we use a "tmp" file here?
> Would it make more sense to chain the 'tr' with 'sed' and skip the
> tmp file ?
>
> tr '\015\000abcdef0123456789' QN00000000000000000 <"$2" |
> sed -e "s/0000*/$ZERO_OID/" >"$exp" &&
>
> Yes, we will loose the exit status of 'tr', I think.
> How important is the exit status ?
As far as I understand, it is only Git commands for which we worry
about losing the exit status upstream in pipes. System utilities, on
the other hand, are presumed to be bug-free, thus we don't mind having
them upstream.
A different question is why does this need to run both 'tr' and 'sed'
when 'sed itself could do the entire job since 'sed' has 'tr'
functionality built in (see sed's "y" command)?
next prev parent reply other threads:[~2018-08-31 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 0:56 [PATCH v3 00/11] Hash-independent tests (part 3) brian m. carlson
2018-08-29 0:56 ` [PATCH v3 01/11] t: add tool to translate hash-related values brian m. carlson
2018-08-29 4:05 ` Jonathan Nieder
2018-08-29 23:22 ` brian m. carlson
2018-08-29 12:37 ` Derrick Stolee
2018-08-29 22:52 ` brian m. carlson
2018-08-29 0:56 ` [PATCH v3 02/11] t0000: use hash translation table brian m. carlson
2018-08-29 0:56 ` [PATCH v3 03/11] t0000: update tests for SHA-256 brian m. carlson
2018-08-29 0:56 ` [PATCH v3 04/11] t0002: abstract away SHA-1 specific constants brian m. carlson
2018-08-29 0:56 ` [PATCH v3 05/11] t0027: make hash size independent brian m. carlson
2018-08-31 18:21 ` Torsten Bögershausen
2018-08-31 18:40 ` Eric Sunshine [this message]
2018-09-01 15:33 ` brian m. carlson
2018-08-29 0:56 ` [PATCH v3 06/11] t0064: " brian m. carlson
2018-08-29 0:56 ` [PATCH v3 07/11] t1006: " brian m. carlson
2018-08-29 0:56 ` [PATCH v3 08/11] t1400: switch hard-coded object ID to variable brian m. carlson
2018-08-29 0:56 ` [PATCH v3 09/11] t1405: make hash size independent brian m. carlson
2018-08-29 0:56 ` [PATCH v3 10/11] t1406: make hash-size independent brian m. carlson
2018-08-29 0:56 ` [PATCH v3 11/11] t1407: make hash size independent 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPig+cSSs9a_RSnc6==zb70Swh1L1Ok4y-DGc8YawPyea0Gm9Q@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=tboegi@web.de \
/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).