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

Re: [PATCH] Fix "git clone" for git:// protocol

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 9, 2008, 18:05 UTC
Message-ID
<alpine.LSU.1.00.0802091805190.11591@racer.site>
In-Reply-To
<alpine.LNX.1.00.0802091205530.13593@iabervon.org>
Hi,
On Sat, 9 Feb 2008, Daniel Barkalow wrote:
Show 18 quoted lines
> On Sat, 9 Feb 2008, Johannes Schindelin wrote:
> 
> > In the commit "Reduce the number of connects when fetching", we 
> > checked the return value of git_connect() to see if the connection was 
> > successful.
> > 
> > However, for the git:// protocol, there is no need to have another 
> > process, so the return value is NULL.
> > 
> > The thing is: git_connect() does not return at all if it fails, so we 
> > need not check the return value of git_connect().
> 
> Huh. Sure enough. Actually, there's a similar problem in transport.c, 
> where it assumes that the return value of git_connect is non-zero, which 
> makes it not reuse the connection (not that you can really tell). It might 
> be good to roll in a fix for that. Or maybe git_connect should return a 
> pointer to a static struct child_process if it doesn't need a subprocess, 
> just to distinguish "we're doing it ourselves" from "it's not being done"? 
Yeah, I like that.  Will do that tomorrow.

Ciao, Dscho

Previous: Daniel BarkalowNext: Johannes Schindelin
Message 3 of 8 in “Fix "git clone" for git:// protocol”
  1. Fix "git clone" for git:// protocolJohannes Schindelin, Feb 9, 2008
  2. Daniel BarkalowFeb 9, 2008
  3. Johannes SchindelinFeb 9, 2008
  4. Fix "git clone" for git:// protocolJohannes Schindelin, Feb 10, 2008
  5. Daniel BarkalowFeb 10, 2008
  6. Junio C HamanoFeb 10, 2008
  7. Johannes SchindelinFeb 10, 2008
  8. Add a test for git-daemon and clone via git:// protocolJohannes Schindelin, Feb 10, 2008

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.