Re: bin/54726: cksum(1) doesn't inform you of passed checks

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR bin/54726; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/54726: cksum(1) doesn't inform you of passed checks
Date: Mon, 02 Dec 2019 07:58:03 +0700

     Date:        Sun,  1 Dec 2019 15:25:01 +0000 (UTC)
     From:        Edgar Pettijohn <edgar%pettijohn-web.com@localhost>
     Message-ID:  <20191201152501.8B4EB7A1AD%mollari.NetBSD.org@localhost>
 
   |  Then why does it give you human readable text for failed files? Seems 
   |  like it should either do both or neither. If neither add a -v flag to 
   |  get both.
 
 It is the philosophy, when all is OK, shut up, when something is wrong,
 say what.   Other tools, like diff, cmp, cc, ... work just the same way.
 
 When everything as it should be, you aren't bothered by meaningless noise.
 When something is not, you get told - which then stands out - it is obvious
 that the message is something to look at.
 
 kre