From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin@catalyst.net.nz>
Cc: git@vger.kernel.org, junkio@cox.net
Subject: Re: [PATCH] git-clone: Error meaningfully on failed HTTP fetches of HEAD
Date: Wed, 11 Apr 2007 17:24:44 -0700 [thread overview]
Message-ID: <7vwt0imoc3.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11763291192402-git-send-email-martin@catalyst.net.nz> (Martin Langhoff's message of "Thu, 12 Apr 2007 10:05:19 +1200")
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?
next prev parent reply other threads:[~2007-04-12 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 22:05 [PATCH] git-clone: Error meaningfully on failed HTTP fetches of HEAD Martin Langhoff
2007-04-12 0:24 ` Junio C Hamano [this message]
2007-04-12 0:28 ` Martin Langhoff
2007-04-12 0:38 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vwt0imoc3.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).