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:26:30 +0100 [thread overview]
Message-ID: <3894968.KDk95S66Zq@nimes> (raw)
In-Reply-To: <01000185f8f5384a-f7e5dfc6-a577-4b21-998d-a0b596056526-000000@email.amazonses.com>
(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
mailing list archive. The commit may have a reference to the mailing
list posting, or you may have to look it up based on the date.
In the other direction, there was coreutils/NEWS change, and from this
commit or its date you can equally navigate to the mailing list posting
and commit on the Gnulib site.
Bruno
next prev parent reply other threads:[~2023-01-28 15:26 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 [this message]
2023-01-28 15:39 ` (GalaxyMaster)
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=3894968.KDk95S66Zq@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).