From: Jeff King <peff@peff.net>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
Sitaram Chamarty <sitaramc@gmail.com>,
git@vger.kernel.org
Subject: Re: clong an empty repo over ssh causes (harmless) fatal
Date: Mon, 31 Aug 2009 18:47:49 -0400 [thread overview]
Message-ID: <20090831224749.GA24190@sigill.intra.peff.net> (raw)
In-Reply-To: <20090831201911.GA24989@atjola.homenet>
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
next prev parent reply other threads:[~2009-08-31 22:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 11:14 clong an empty repo over ssh causes (harmless) fatal Sitaram Chamarty
2009-08-31 11:22 ` Matthieu Moy
2009-08-31 14:30 ` Sitaram Chamarty
2009-08-31 14:47 ` Matthieu Moy
2009-08-31 16:41 ` Jeff King
2009-08-31 17:12 ` Sverre Rabbelier
2009-08-31 19:08 ` Jeff King
2009-08-31 19:09 ` Sverre Rabbelier
2009-08-31 17:25 ` Matthieu Moy
2009-08-31 19:10 ` Jeff King
2009-08-31 20:19 ` Björn Steinbrink
2009-08-31 22:47 ` Jeff King [this message]
2009-08-31 22:50 ` Sverre Rabbelier
2009-09-01 1:08 ` Jeff King
2009-09-02 4:33 ` Daniel Barkalow
2009-09-02 5:16 ` Jeff King
2009-09-02 6:02 ` Daniel Barkalow
2009-09-02 6:36 ` [PATCH] clone: disconnect transport after fetching Jeff King
2009-09-02 7:09 ` Sverre Rabbelier
2009-09-02 7:26 ` Jeff King
2009-09-02 7:37 ` Sverre Rabbelier
2009-09-02 16:38 ` Daniel Barkalow
2009-09-02 17:55 ` Junio C Hamano
2009-09-04 2:30 ` Jeff King
2009-09-02 5:30 ` clong an empty repo over ssh causes (harmless) fatal Sitaram Chamarty
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=20090831224749.GA24190@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=B.Steinbrink@gmx.de \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
--cc=srabbelier@gmail.com \
/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).