bug-coreutils@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Ricardo Branco <rbranco@suse.de>
To: "Pádraig Brady" <P@draigBrady.com>, 69368@debbugs.gnu.org
Subject: bug#69368: [PATCH] Allow --zero with --check
Date: Sun, 25 Feb 2024 12:13:17 +0100	[thread overview]
Message-ID: <b40fd0ae-0a08-4748-9bef-8b98e70284c7@suse.de> (raw)
In-Reply-To: <5a23db51-3258-f2de-6556-f680c480b001@draigBrady.com>


On 2/25/24 12:06, Pádraig Brady wrote:
> By adding this support we diverge the checksum file formats supported 
> by check.
> I.e. users may inadvertently create such files that are not usable
> by any previous version of the checksum utilities.

Any user of the --zero flag has already created completely unusable 
check files.

This patch makes them usable.

> Also having --check support NUL delimited files
> doesn't add any additional functionality, as the checksum files
> are already automatically escaped appropriately.

The --zero flag disables file name escaping.

> Also NUL delimited checksum files can be harder to manage with other 
> text tools.

Only text tools that don't have zero flags unlike the ones you mention here:

> --zero was added for the case of piping to other tools
> that would find the filename escaping problematic.


Best,

R





      reply	other threads:[~2024-02-25 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 19:07 bug#69368: [PATCH] Allow --zero with --check Ricardo Branco
2024-02-25 10:29 ` bug#69368: [PATCH]: md5sum: " Ricardo Branco
2024-02-25 11:06 ` bug#69368: [PATCH] " Pádraig Brady
2024-02-25 11:13   ` Ricardo Branco [this message]

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: https://lists.gnu.org/mailman/listinfo/bug-coreutils

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b40fd0ae-0a08-4748-9bef-8b98e70284c7@suse.de \
    --to=rbranco@suse.de \
    --cc=69368@debbugs.gnu.org \
    --cc=P@draigBrady.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 read-only IMAP folder(s) and NNTP newsgroup(s).