On Mon, Aug 31, 2009 at 10:19:11PM +0200, Björn Steinbrink wrote: > 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 OK, it is definitely not about mixed versions, and it is definitely reproducible, even without ssh. The local clone optimization manages to avoid it, but you can see it with: git clone file://$PWD/a b It also happens with git://, except that it is the _remote_ side producing the message, so git-daemon gets "the remote end hung up unexpectedly" on its stderr channel. AFAICT, this problem goes back to v1.6.2, the first version which handled empty clones. So I blame Sverre. ;) -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html