Re: clong an empty repo over ssh causes (harmless) fatal
- From
Björn Steinbrink <b.steinbrink@gmx.de>
- Date
- Aug 31, 2009, 20:19 UTC
- Message-ID
- <20090831201911.GA24989@atjola.homenet>
- In-Reply-To
- <20090831191032.GB4876@sigill.intra.peff.net>
On 2009.08.31 15:10:32 -0400, Jeff King wrote:
Show 14 quoted lines
> On Mon, Aug 31, 2009 at 07:25:22PM +0200, Matthieu Moy wrote: > > > Since the client and server are the same machine: > > > > $ git clone ssh://sitaram@localhost/home/sitaram/t/a b > > > > I'd bet Sitaram has two installations of git, and plain ssh to the > > machine points to the old one (like a $PATH set in ~/.login and not > > ~/.profile or something like that). > > Oh, indeed. I didn't notice that his host was @localhost. :) > > But yes, that would be my guess, as well. Trying "ssh sitaram@localhost > git version" would be a good clue.
I see the problem here, too.
doener@atjola:~ $ (mkdir a; cd a; git init) Initialized empty Git repository in /home/doener/a/.git/
doener@atjola:~ $ git clone localhost:a b Initialized empty Git repository in /home/doener/b/.git/ warning: You appear to have cloned an empty repository. fatal: The remote end hung up unexpectedly
doener@atjola:~ $ ssh localhost git --version git version 1.6.4.2.236.gf324c
Björn