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

Re: [PATCH] git-clone: Error meaningfully on failed HTTP fetches of HEAD

From
Junio C Hamano <junkio@cox.net>
Date
Apr 12, 2007, 00:24 UTC
Message-ID
<7vwt0imoc3.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<11763291192402-git-send-email-martin@catalyst.net.nz>
Martin Langhoff <martin@catalyst.net.nz> writes:
Show 11 quoted lines
> A common problem when cloning over http is that the repo has
> a symlink for HEAD, and apache refuses to serve symlinks by
> default.
>
> Without this patch, the clone succeeds as a "bare" and "HEADless"
> clone, but does not give any indication that things have gone
> wrong.
>
> A bare clone that fails to fetch HEAD will still complete
> "successfully". I'm not sure if that's expected/desired. Is a
> HEADless repo valid in any situation?

You would get "fatal: Not a git repository". Why not default to 'master' (if found) and issue a warning?

Previous: Martin LanghoffNext: Martin Langhoff
Message 2 of 4 in “git-clone: Error meaningfully on failed HTTP fetches of HEAD”
  1. git-clone: Error meaningfully on failed HTTP fetches of HEADMartin Langhoff, Apr 11, 2007
  2. Junio C HamanoApr 12, 2007
  3. Martin LanghoffApr 12, 2007
  4. Junio C HamanoApr 12, 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.