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

Re: [PATCH] git-fetch: resolve remote symrefs for HTTP transport

From
Shawn Pearce <spearce@spearce.org>
Date
Apr 26, 2006, 17:09 UTC
Message-ID
<20060426170946.GA7843@spearce.org>
In-Reply-To
<20060426161001.GH32744@reactrix.com>
Nick Hengeveld <nickh@reactrix.com> wrote:
> 
> Maybe this isn't the right way to handle this - since we're already
> calling perl we could use LWP to do the transfers (using keepalive
> even?)

LWP, no. My Mac OS X perl installation appears to have LWP installed by dumb luck but my Gentoo Linux perl doesn't have LWP anywhere in @INC. :-) Yet both systems run GIT happily.

The HTTP support in GIT is already linked against libcurl and libcurl is required to use said HTTP support. I would think that libcurl is capable of using Keep-Alive when possible, and libcurl and C are certainly available anywhere GIT's HTTP support is currently being used. Ideally any HTTP feature should either be using the curl command line tool, or better, be written in C against the libcurl library. But not LWP. Its not always available even though a valid perl is.

-- 
Shawn.
Previous: Nick Hengeveld
Message 2 of 2 in “git-fetch: resolve remote symrefs for HTTP transport”
  1. git-fetch: resolve remote symrefs for HTTP transportNick Hengeveld, Apr 26, 2006
  2. Shawn PearceApr 26, 2006

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.