git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: "Jonathan Nieder" <jrnieder@gmail.com>, "René Scharfe" <l.s.r@web.de>
Cc: Git List <git@vger.kernel.org>,
	Benoit Lecocq <benoit@openbsd.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] t1002: stop using sum(1)
Date: Tue, 15 Aug 2017 08:27:35 +0200	[thread overview]
Message-ID: <53a9a3cd-f814-47a3-cc9b-977f9107614c@kdbg.org> (raw)
In-Reply-To: <20170815004546.GA78174@aiede.mtv.corp.google.com>

Am 15.08.2017 um 02:46 schrieb Jonathan Nieder:
> Hi,
> 
> René Scharfe wrote:
> 
>> sum(1) is a command for calculating checksums of the contents of files.
>> It was part of early editions of Unix ("Research Unix", 1972/1973, [1]).
>> cksum(1) appeared in 4.4BSD (1993) as a replacement [2], and became part
>> of POSIX.1-2008 [3].  OpenBSD 5.6 (2014) removed sum(1).
>>
>> We only use sum(1) in t1002 to check for changes in three files.  On
>> MinGW we use md5sum(1) instead.  We could switch to the standard command
>> cksum(1) for all platforms; MinGW comes with GNU coreutils now, which
>> provides sum(1), cksum(1) and md5sum(1).  Use our standard method for
>> checking for file changes instead: test_cmp.
>>
>> It's more convenient because it shows differences nicely, it's faster on
>> MinGW because we have a special implementation there based only on
>> shell-internal commands, it's simpler as it allows us to avoid stripping
>> out unnecessary entries from the checksum file using grep(1), and it's
>> more consistent with the rest of the test suite.
>>
>> We already compare changed files with their expected new contents using
>> diff(1), so we don't need to check with "test_must_fail test_cmp" if
>> they differ from their original state.  A later patch could convert the
>> direct diff(1) calls to test_cmp as well.
>>
>> With all sum(1) calls gone, remove the MinGW-specific implementation
>> from test-lib.sh as well.
>>
>> [1] http://minnie.tuhs.org/cgi-bin/utree.pl?file=V3/man/man1/sum.1
>> [2] http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.4BSD/usr/share/man/cat1/cksum.0
>> [3] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/cksum.html
>> ---
>>   t/t1002-read-tree-m-u-2way.sh | 67 ++++++++++++++++++++++---------------------
>>   t/test-lib.sh                 |  3 --
>>   2 files changed, 35 insertions(+), 35 deletions(-)
> 
> Nicely analyzed.  May we forge your sign-off?
> 
> [...]
>> --- a/t/t1002-read-tree-m-u-2way.sh
>> +++ b/t/t1002-read-tree-m-u-2way.sh
> [...]
>> @@ -132,8 +138,8 @@ test_expect_success \
>>        git ls-files --stage >7.out &&
>>        test_cmp M.out 7.out &&
>>        check_cache_at frotz dirty &&
>> -     sum bozbar frotz nitfol >actual7.sum &&
>> -     if cmp M.sum actual7.sum; then false; else :; fi &&
>> +     test_cmp bozbar.M bozbar &&
>> +     test_cmp nitfol.M nitfol &&
> 
> This one is strange.  What is that '! cmp' trying to check for?
> Does the replacement capture the same thing?
> 
> E.g., does it need a '! test_cmp frotz.M frotz &&' line?

In the context that you stripped a 'diff frotz frotz1' occurs, i.e., a 
check for the expected content of the file whose content changes. 
Together with the new test_cmp lines, the new text is a stricter check 
than we have in the old text.

The patch looks good.

Reviewed-by: Johannes Sixt <j6t@kdbg.org>

-- Hannes

  reply	other threads:[~2017-08-15  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 20:16 [PATCH] t1002: stop using sum(1) René Scharfe
2017-08-14 20:35 ` Junio C Hamano
2017-08-15  0:46 ` Jonathan Nieder
2017-08-15  6:27   ` Johannes Sixt [this message]
2017-08-15 14:43   ` René Scharfe
2017-08-15 14:37 ` René Scharfe

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=53a9a3cd-f814-47a3-cc9b-977f9107614c@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=benoit@openbsd.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=l.s.r@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.
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).