From: Jeff King <peff@peff.net>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Possibly solved invalid free() in git-remote-http from Git 1.7.2.1
Date: Mon, 1 Aug 2011 21:33:44 -0600 [thread overview]
Message-ID: <20110802033344.GA17494@sigill.intra.peff.net> (raw)
In-Reply-To: <20110802105124.000021c3@unknown>
On Tue, Aug 02, 2011 at 10:51:24AM +0800, Tay Ray Chuan wrote:
> On Mon, 1 Aug 2011 12:00:19 -0600
> Jeff King <peff@peff.net> wrote:
> > Hmm. The memory management in the function seems weird to me.
>
> How about this?
Yes, that fixes all of the oddities I found (I assume you looked and
agreed with me that they were wrong).
-Peff
next prev parent reply other threads:[~2011-08-02 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 15:22 Possibly solved invalid free() in git-remote-http from Git 1.7.2.1 Ævar Arnfjörð Bjarmason
2011-08-01 15:39 ` Ævar Arnfjörð Bjarmason
2011-08-01 15:42 ` Ævar Arnfjörð Bjarmason
2011-08-01 18:00 ` Jeff King
2011-08-02 2:51 ` Tay Ray Chuan
2011-08-02 3:33 ` Jeff King [this message]
2011-08-03 11:54 ` [PATCH] http.c: fix an invalid free() Tay Ray Chuan
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=20110802033344.GA17494@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.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;
as well as URLs for NNTP newsgroup(s).