From: Jim Meyering <jim@meyering.net>
To: "bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: any pending fixes? preparing for diffutils release
Date: Sun, 1 Aug 2021 12:44:08 -0700 [thread overview]
Message-ID: <CA+8g5KGbCS=y=o2a5r5yL=59gLQ+Q8bvVVh04kte5+eMCgKwig@mail.gmail.com> (raw)
I am ready to release diffutils-3.8, but in order to get it to compile
warning-free with configure's --enable-gcc-warnings and GCC 11.2.1, I
had to push another -fanalyze-pacification patch to regex_internal.c,
just minutes ago. Given that this made diffutils pull in gnulib
changes since the snapshot of two weeks ago, I considered first
creating another snapshot. But nothing recent seems particularly
risky, so I'll probably go ahead with the release today. At worst,
I'll make another release in a week or two.
But first, does anyone have anything pending that I should be sure to include?
Thanks,
Jim
next reply other threads:[~2021-08-01 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 19:44 Jim Meyering [this message]
2021-08-01 22:14 ` any pending fixes? preparing for diffutils release Paul Eggert
2021-08-02 0:53 ` Jim Meyering
2021-08-02 5:36 ` Paul Eggert
2021-08-02 5:48 ` Jim Meyering
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='CA+8g5KGbCS=y=o2a5r5yL=59gLQ+Q8bvVVh04kte5+eMCgKwig@mail.gmail.com' \
--to=jim@meyering.net \
--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).