From: Mike Stump <mikestump@comcast.net>
To: Jim Meyering <jim@meyering.net>
Cc: gcc-patches Patches <gcc-patches@gcc.gnu.org>,
DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH] avoid memory overrun in a test leading to potential double-free
Date: Sun, 10 Apr 2011 18:16:00 -0000 [thread overview]
Message-ID: <12EF385F-0775-4561-B885-03965828E935@comcast.net> (raw)
In-Reply-To: <201103081923.p28JNIBD026445@greed.delorie.com>
On Mar 8, 2011, at 11:23 AM, DJ Delorie wrote:
>> 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.
>
> Ok. Thanks!
Applied, thanks. In general, you have to ask someone to apply things for you, if you can't actually do the checkin, after a patch is approved.
prev parent reply other threads:[~2011-04-10 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 12:59 Jim Meyering
2011-03-08 19:23 ` DJ Delorie
2011-04-10 18:16 ` Mike Stump [this message]
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=12EF385F-0775-4561-B885-03965828E935@comcast.net \
--to=mikestump@comcast.net \
--cc=dj@redhat.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).