On 28/10/15 06:40, Bernhard Voelker wrote:
> On 10/27/2015 06:21 PM, Pádraig Brady wrote:
>> On 26/10/15 07:11, Bernhard Voelker wrote:
>>> BTW: I was quite surprised to see that the other utilities -
>>> sha{224,256,384,512}sum - don't have a single negative test.
>>> I mean, there should be at
On 10/27/2015 06:21 PM, Pádraig Brady wrote:
> On 26/10/15 07:11, Bernhard Voelker wrote:
>> BTW: I was quite surprised to see that the other utilities -
>> sha{224,256,384,512}sum - don't have a single negative test.
>> I mean, there should be at least one case for each of these
>> utilities to
On 26/10/15 07:11, Bernhard Voelker wrote:
> On 10/26/2015 02:51 AM, Pádraig Brady wrote:
>> From 5e3d017e7bc66cf6f666160f774944c2ff52d1ae Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?P=C3=A1draig=20Brady?=
>> Date: Mon, 26 Oct 2015 01:26:04 +
>> Subject: [PATCH] md5sum:
On 10/26/2015 02:51 AM, Pádraig Brady wrote:
> From 5e3d017e7bc66cf6f666160f774944c2ff52d1ae Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?P=C3=A1draig=20Brady?=
> Date: Mon, 26 Oct 2015 01:26:04 +
> Subject: [PATCH] md5sum: quote all printed file names
>
> This is
On 25/10/15 18:05, MI wrote:
> Currently, "md5sum -c" gives a cryptic error when the line endings in the
> .md5 file
> are not LF (\x0A). It would be helpful if md5sum would just "do the right"
> and
> understand the 2 other newline standards.
>
> .md5 files created on non-Unix systems may
Currently, "md5sum -c" gives a cryptic error when the line endings in the .md5 file
are not LF (\x0A). It would be helpful if md5sum would just "do the right" and
understand the 2 other newline standards.
.md5 files created on non-Unix systems may use line endings other than LF . Windows
uses