From: Junio C Hamano <junkio@cox.net>
Date: Thu, 12 Apr 2007 00:24:44 GMT
Subject: Re: [PATCH] git-clone: Error meaningfully on failed HTTP fetches of HEAD
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:

> 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?