From: "(GalaxyMaster)" <galaxy@openwall.com.au>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: filevercmp incompatible change?
Date: Sat, 28 Jan 2023 15:39:54 +0000 [thread overview]
Message-ID: <01000185f908fd47-5b8bfdfb-3822-40ea-aab2-6db7d3d03c6a-000000@email.amazonses.com> (raw)
In-Reply-To: <3894968.KDk95S66Zq@nimes>
On Sat, Jan 28, 2023 at 04:26:30PM +0100, Bruno Haible wrote:
> (GalaxyMaster) wrote:
> > I spent almost an hour before I pinpointed it to filevercmp.c
>
> In order to understand a commit, you typically need to navigate to the
Oh, I don't have any issues with commits and source code, it is the time to
locate why something is not working as expected. In case of the version sort
test in coreutils, it required me to trace ls and see what functions it is
calling for the version sort, then I searched for commits and found the change.
I looked at the messages from the report of the bug till Paul fixed it, but a
crucial part of the knowledge was still missing -- it is the expected sorting
order of this Debian sort (without reading into the specification it is not
clear what the expected order is supposed to be).
Anyway, thanks. All is good now.
--
(GM)
next prev parent reply other threads:[~2023-01-28 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230128145803.GF15496@mail.openwall.com.au>
2023-01-28 15:18 ` filevercmp incompatible change? (GalaxyMaster)
2023-01-28 15:26 ` Bruno Haible
2023-01-28 15:39 ` (GalaxyMaster) [this message]
2023-01-28 14:58 (GalaxyMaster)
2023-01-28 15:20 ` Bruno Haible
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=01000185f908fd47-5b8bfdfb-3822-40ea-aab2-6db7d3d03c6a-000000@email.amazonses.com \
--to=galaxy@openwall.com.au \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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).