Re: [PATCH] git-clone: Error meaningfully on failed HTTP fetches of HEAD
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:04
Martin Langhoff [off-list ref] 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?