From: "Torsten Bögershausen" <tboegi@web.de>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"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 20:21:41 +0200 [thread overview]
Message-ID: <20180831182141.GA9399@tor.lan> (raw)
In-Reply-To: <20180829005642.980617-6-sandals@crustytoothpaste.net>
On Wed, Aug 29, 2018 at 12:56:36AM +0000, brian m. carlson wrote:
> We transform various object IDs into all-zero object IDs for comparison.
> Adjust the length as well so that this works for all hash algorithms.
>
> Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
> ---
> t/t0027-auto-crlf.sh | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/t/t0027-auto-crlf.sh b/t/t0027-auto-crlf.sh
> index beb5927f77..0f1235d9d1 100755
> --- a/t/t0027-auto-crlf.sh
> +++ b/t/t0027-auto-crlf.sh
> @@ -14,11 +14,13 @@ compare_files () {
> compare_ws_file () {
> pfx=$1
> exp=$2.expect
> + 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" &&
> test_cmp "$exp" "$act" &&
> - rm "$exp" "$act"
> + rm "$exp" "$act" "$tmp"
> }
>
> create_gitattributes () {
I only managed to review the changes in t0027.
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 ?
I don't know, hopefully someone with more experience/knowledge
about shell scripting can help me out here.
next prev parent reply other threads:[~2018-08-31 18:27 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 [this message]
2018-08-31 18:40 ` Eric Sunshine
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=20180831182141.GA9399@tor.lan \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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.
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).