git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Use libcurl to use HTTP to get repositories

From
IMIngo Molnar <mingo@elte.hu>
Date
Apr 17, 2005, 04:55 UTC
Message-ID
<20050417045559.GA769@elte.hu>
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
Previous: Linus Torvalds
Message 6 of 6 in “Use libcurl to use HTTP to get repositories”
  1. Use libcurl to use HTTP to get repositoriesDaniel Barkalow, Apr 17, 2005
  2. Paul JacksonApr 17, 2005
  3. Daniel BarkalowApr 17, 2005
  4. Paul JacksonApr 17, 2005
  5. Linus TorvaldsApr 17, 2005
  6. Ingo MolnarApr 17, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.