Re: Cloning empty repositories, was Re: What is the idea for bare repositories?

From: Jeff King <peff@peff.net>
Date: Nov 18, 2007, 03:25 UTC
Message-ID: <20071118032547.GC4560@sigill.intra.peff.net>
In-Reply-To: <7vejeoz7is.fsf@gitster.siamese.dyndns.org>

On Sat, Nov 17, 2007 at 05:06:51PM -0800, Junio C Hamano wrote:

Show 6 quoted lines

> > Junio, can I get an ACK or NAK on the patch below?
> 
> I do not think it would hurt.  Is the "local" case the only
> codepath that needs this (iow, we would not need this message if
> other transports die more loudly and/or we cannot tell if the
> failure is wrong URL or empty remote repository)?

Good question, and the answer is yes, it is the only spot that produces no useful output. The other errors are:

via ssh, git-daemon, or file:// (all using receive-pack) you get: $ git-clone localhost:foo bar Initialized empty Git repository in /home/peff/bar/.git/ fatal: no matching remote head fetch-pack from 'localhost:foo' failed.

via http, you get: $ git-clone http://localhost/git/foo bar Initialized empty Git repository in /home/peff/bar/.git/ Cannot get remote repository information. Perhaps git-update-server-info needs to be run there?

I didn't try rsync, though I expect it should be the same as http.

-Peff