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

[PATCH 0/5] Return of 'quickfetch' version 3

From
Shawn O. Pearce <spearce@spearce.org>
Date
Nov 11, 2007, 07:29 UTC
Message-ID
<20071111072913.GX14735@spearce.org>

OK, attempt #3. Much shorter series as I've taken out the (messy) object memory management change. Its now unrelated to this series and may return in the near future.

 1) Fix memory leak in traverse_commit_list

The memory leak we talked about in traverse_commit_list. Its still valid for pack-objects but is unnecessary for fetch.

 2) git-fetch: Always fetch tags if the object they reference exists

I think I figured out why I said "random behavior" earlier. Please see the commit message for an updated description.

 3) run-command: Support sending stderr to /dev/null
 4) rev-list: Introduce --quiet to avoid /dev/null redirects
 5) git-fetch: avoid local fetching from alternate (again)

Pretty much the original quickfetch series, but updated with list comments and moved to builtin-fetch where it works for all types of transports and not just the native git one.

-- 
Shawn.
Message 1 of 1 in “Return of 'quickfetch' version 3”
  1. 0/5 Return of 'quickfetch' version 3Shawn O. Pearce, Nov 11, 2007

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.