From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] hexedit: avoid NULL dereference upon failed malloc
Date: Thu, 02 Jul 2009 13:05:36 +0200 [thread overview]
Message-ID: <87fxdfuyyn.fsf@meyering.net> (raw)
In-Reply-To: <1246527478.3379.1.camel@localhost.localdomain> (Steven Whitehouse's message of "Thu, 02 Jul 2009 10:37:58 +0100")
Steven Whitehouse wrote:
> Also looks good to me,
Pushed, too.
Thanks.
next prev parent reply other threads:[~2009-07-02 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 7:40 [Cluster-devel] [PATCH] hexedit: avoid NULL dereference upon failed malloc Jim Meyering
2009-07-02 9:37 ` Steven Whitehouse
2009-07-02 11:05 ` Jim Meyering [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-17 16:00 Jim Meyering
2009-06-19 6:11 ` Andrew Price
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=87fxdfuyyn.fsf@meyering.net \
--to=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