From: Bruno Haible <bruno@clisp.org>
To: "(GalaxyMaster)" <galaxy@openwall.com.au>
Cc: bug-gnulib@gnu.org
Subject: Re: filevercmp incompatible change?
Date: Sat, 28 Jan 2023 16:20:11 +0100 [thread overview]
Message-ID: <4598695.WzN2syfzKT@nimes> (raw)
In-Reply-To: <01000185f8e2b1b4-becc9439-2f82-4857-a302-55cda9e1574e-000000@email.amazonses.com>
Hi,
(GalaxyMaster) wrote:
> I think the following commit introduced a behavioural change that was not
> intended: https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=1ba2b66ea45f9bc43cdc0f6f93efa59157d2b2ba
The patch modified a unit test. This means that the change was intended.
Also it was discussed in this thread:
https://lists.gnu.org/archive/html/bug-gnulib/2022-06/msg00019.html
and accompanied with a coreutils change:
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=0ae619f3495dd9456e4a58226e16d3260b623a78
Bruno
next prev parent reply other threads:[~2023-01-28 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 14:58 filevercmp incompatible change? (GalaxyMaster)
2023-01-28 15:20 ` Bruno Haible [this message]
[not found] <20230128145803.GF15496@mail.openwall.com.au>
2023-01-28 15:18 ` (GalaxyMaster)
2023-01-28 15:26 ` Bruno Haible
2023-01-28 15:39 ` (GalaxyMaster)
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-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4598695.WzN2syfzKT@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=galaxy@openwall.com.au \
/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).