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

Re: git clone problem through HTTP

From
Junio C Hamano <junkio@cox.net>
Date
Apr 20, 2007, 21:31 UTC
Message-ID
<7vd51yybpf.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vodliyd1j.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 25 quoted lines
> [[manual workaround to make it work with existing tools]]
> ... should work, because I knew about this problem and fixed it in
> git-fetch in v1.5.0.
>
> Alas, I forgot to update the matching code in git-clone.
>
> This is why I keep saying that we should get rid of as much code
> from git-clone, and make it essentially a thin wrapper around
> the six commands I quoted above.
>
> ---
>
> diff --git a/git-clone.sh b/git-clone.sh
> index 513b574..cad5c0c 100755
> --- a/git-clone.sh
> +++ b/git-clone.sh
> @@ -60,7 +60,7 @@ Perhaps git-update-server-info needs to be run there?"
>  		else
>  			tname=$name
>  		fi
> -		git-http-fetch $v -a -w "$tname" "$name" "$1" || exit 1
> +		git-http-fetch $v -a -w "$tname" "$sha1" "$1" || exit 1
>  	done <"$clone_tmp/refs"
>  	rm -fr "$clone_tmp"
>  	http_fetch "$1/HEAD" "$GIT_DIR/REMOTE_HEAD" ||

I've applied the above patch on top of 'maint' and it clones Linus's reopsitory over http just fine. I will include this fix in upcoming maintenance release v1.5.1.2.

Thanks for reporting the breakage.
Previous: Junio C HamanoNext: Aubrey Li
Message 10 of 11 in “git clone problem through HTTP”
  1. Aubrey LiApr 20, 2007
  2. Julian PhillipsApr 20, 2007
  3. Medve Emilian-EMMEDVE1Apr 20, 2007
  4. Aubrey LiApr 20, 2007
  5. Alex RiesenApr 20, 2007
  6. Brian GernhardtApr 20, 2007
  7. Julian PhillipsApr 20, 2007
  8. Junio C HamanoApr 20, 2007
  9. Junio C HamanoApr 20, 2007
  10. Junio C HamanoApr 20, 2007
  11. Aubrey LiApr 22, 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.