From: Jim Meyering <jim@meyering.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: any pending fixes? preparing for diffutils release
Date: Sun, 1 Aug 2021 17:53:13 -0700 [thread overview]
Message-ID: <CA+8g5KFfQPbT3QJTFPe-FMVYTbs=3eqwMyzKa3HpwJJSw_Z4fQ@mail.gmail.com> (raw)
In-Reply-To: <f1d70ad6-0a9e-475d-8b83-41006c691b2f@cs.ucla.edu>
On Sun, Aug 1, 2021 at 3:15 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
> I've recently been improving some GCC-based static analysis in Gnulib,
Welcome changes. Thanks!
> and syncing from Gnulib to diffutils meant that you have a bit of a
> work-in-progress there. I plan to make further such changes soon.
No problem, of course.
> The Gnulib work already installed is conservative and I see no harm in
> releasing what we've got in diffutils now. I'm sending this email mainly
> to give you a heads-up that more Gnulib changes are coming.
>
> FWIW attached are the diffutils patches I have so far. They assume the
> abovementioned Gnulib work-in-progress and this should not be installed
> in diffutils yet. Most likely more minor diffutils patches will be
> needed once I've finished the Gnulib changes I have in mind.
>
> Until today I've been using the Gnulib work-in-progress on grep rather
> than on diffutils. I've found one memory leak there and hope to find
> more bugs - after all, that's the point of all this. I didn't find any
> diffutils bugs in my brief run-through today.
Good. Thanks again.
next prev parent reply other threads:[~2021-08-02 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 19:44 any pending fixes? preparing for diffutils release Jim Meyering
2021-08-01 22:14 ` Paul Eggert
2021-08-02 0:53 ` Jim Meyering [this message]
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+8g5KFfQPbT3QJTFPe-FMVYTbs=3eqwMyzKa3HpwJJSw_Z4fQ@mail.gmail.com' \
--to=jim@meyering.net \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).