From: Jim Meyering <jim@meyering.net>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] avoid a few strncpy-induced buffer overruns
Date: Wed, 25 Apr 2012 08:23:00 -0000 [thread overview]
Message-ID: <877gx45im0.fsf@rho.meyering.net> (raw)
In-Reply-To: <87wr54dhbq.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 24 Apr 2012 14:07:37 -0600")
Tom Tromey wrote:
>>>>>> "Jim" == Jim Meyering <jim@meyering.net> writes:
>
> Jim> I've been on a little crusade to avoid strncpy abuse
> Jim> and spotted/fixed a few uses here.
>
> This is ok. Thanks.
Thanks for the quick review.
I've cvs-committed that.
cvs feels so clunky and archaic, now...
next prev parent reply other threads:[~2012-04-25 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 19:27 Jim Meyering
2012-04-24 20:17 ` Tom Tromey
2012-04-25 8:23 ` Jim Meyering [this message]
2012-04-25 15:04 ` Joel Brobecker
2012-04-25 15:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gx45im0.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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