Re: clong an empty repo over ssh causes (harmless) fatal

Sitaram Chamarty [off-list ref] writes:

Hello,

Cloning an empty repo seems to produce a spurious error.
The repo still seems fine though.

Can't reproduce here:

$ git clone ssh://.../tmp/empty cloned
Initialized empty Git repository in /tmp/cloned/.git/
warning: You appear to have cloned an empty repository.
$ git --version
git version 1.6.4.187.gd399.dirty

Maybe you have an older version of Git?

-- 
Matthieu

[apologies if you get this twice]

On Mon, Aug 31, 2009 at 4:52 PM, Matthieu Moy [off-list ref] wrote:

Sitaram Chamarty [off-list ref] writes:

quoted

Hello,

Cloning an empty repo seems to produce a spurious error.
The repo still seems fine though.

Can't reproduce here:

$ git clone ssh://.../tmp/empty cloned
Initialized empty Git repository in /tmp/cloned/.git/
warning: You appear to have cloned an empty repository.
$ git --version
git version 1.6.4.187.gd399.dirty

Maybe you have an older version of Git?

Had 1.6.4, just tried with 1.6.4.2 -- the error is still there, exactly so.

Anything I can do to provide more info?

To start with, this is Mandriva 2009.1, kernel 2.6.29, git built from
scratch locally (not an RPM or something).  Should I try some other
things like strace?  It's too minor to bother, if that's all it is,
assuming it's not a symptom of something larger :)

--
Matthieu

On Mon, Aug 31, 2009 at 08:00:41PM +0530, Sitaram Chamarty wrote:

quoted

Maybe you have an older version of Git?

Had 1.6.4, just tried with 1.6.4.2 -- the error is still there, exactly so.

Anything I can do to provide more info?

IIRC, the message you are seeing comes when the _server_ is an older
version of git. It is harmless, though.

-Peff

Heya,

On Mon, Aug 31, 2009 at 18:41, Jeff King[off-list ref] wrote:

IIRC, the message you are seeing comes when the _server_ is an older
version of git. It is harmless, though.

Mhhhh, is it some weird interaction between 'empty repository' patch
and old server versions, or did this happen too before my patch was
applied?

-- 
Cheers,

Sverre Rabbelier

On Mon, Aug 31, 2009 at 07:12:44PM +0200, Sverre Rabbelier wrote:

On Mon, Aug 31, 2009 at 18:41, Jeff King[off-list ref] wrote:

quoted

IIRC, the message you are seeing comes when the _server_ is an older
version of git. It is harmless, though.

Mhhhh, is it some weird interaction between 'empty repository' patch
and old server versions, or did this happen too before my patch was
applied?

I think the former. I thought it was discussed before, but the only
reference I can find is this (see the end of the email):

  http://article.gmane.org/gmane.comp.version-control.git/107626

and I don't see any followup for that specific part of the mail.

-Peff

Heya,

On Mon, Aug 31, 2009 at 21:08, Jeff King[off-list ref] wrote:

I think the former. I thought it was discussed before, but the only
reference I can find is this (see the end of the email):

 http://article.gmane.org/gmane.comp.version-control.git/107626

Ah, yeup, I see.

and I don't see any followup for that specific part of the mail.

I don't remember any follow up to that either, shame on me :(.

-- 
Cheers,

Sverre Rabbelier