From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jim Meyering <jim@meyering.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: doubled words
Date: Sun, 10 Apr 2011 19:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1104101926560.10984@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87wrj2nwxq.fsf@rho.meyering.net>
On Sun, 10 Apr 2011, Jim Meyering wrote:
> I would be inclined to prepare a patch if I thought it would
> be applied (promptly?), but I submitted a clear/simple fix for
> an obvious double-free bug (albeit only in a test case) a month ago:
>
> http://patchwork.ozlabs.org/patch/85973/
> avoid memory overrun in a test leading to potential double-free
> * testsuite/test-expandargv.c (writeout_test): Fix off-by-one error:
> i.e., do copy the trailing NUL byte.
>
> AFAIK, it hasn't been applied. If a "real" bug has such low priority,
> this is not a good time to submit a clean-up change.
Please ping unreviewed (or approved but not committed) patches at least
weekly, as many times as needed. If a patch isn't reviewed within a week,
it's unlikely to be reviewed without a ping. (Actually I suspect the vast
bulk of reviews are within two or three days.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-04-10 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 11:55 Jim Meyering
2011-04-10 18:01 ` Mike Stump
2011-04-10 21:07 ` Jim Meyering
2011-04-23 7:48 ` Mike Stump
2011-04-23 9:08 ` Jim Meyering
2011-04-10 18:21 ` Mike Stump
2011-04-10 19:07 ` Mike Stump
2011-04-10 20:42 ` Jim Meyering
2011-04-10 19:28 ` Joseph S. Myers [this message]
2011-04-10 19:34 ` Joseph S. Myers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1104101926560.10984@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim@meyering.net \
/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).