From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH] Use libcurl to use HTTP to get repositories
Date: Sun, 17 Apr 2005 06:55:59 +0200 [thread overview]
Message-ID: <20050417045559.GA769@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.21.0504162008190.30848-100000@iabervon.org>
* Daniel Barkalow <barkalow@iabervon.org> wrote:
> Still leaks a bit of memory due to bug copied from read-tree.
Linus, should i resend the 18 fixes i sent the other day? (as a GIT
repository perhaps?) I found roughly 6 common memory leaks, 8
theoretical memory leaks, 2 overflows and did a couple of cleanups. One
of the patches [the cache collision related thing] we agreed was not
needed, the rest is still very much valid i think. I did some basic
testing with the fixes applied, nothing seemed to break in any visible
way in these tests.
Ingo
prev parent reply other threads:[~2005-04-17 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 0:14 [PATCH] Use libcurl to use HTTP to get repositories Daniel Barkalow
2005-04-17 0:29 ` Paul Jackson
2005-04-17 0:42 ` Daniel Barkalow
2005-04-17 0:45 ` Paul Jackson
2005-04-17 4:36 ` Linus Torvalds
2005-04-17 4:55 ` Ingo Molnar [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=20050417045559.GA769@elte.hu \
--to=mingo@elte.hu \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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).