Re: clong an empty repo over ssh causes (harmless) fatal
- From
Sitaram Chamarty <sitaramc@gmail.com>
- Date
- Aug 31, 2009, 14:30 UTC
- Message-ID
- <2e24e5b90908310730u53ee27d3nd2b66c1f58202e7@mail.gmail.com>
- In-Reply-To
- <vpqskf8z0rj.fsf@bauges.imag.fr>
[apologies if you get this twice]
On Mon, Aug 31, 2009 at 4:52 PM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
Show 17 quoted lines
> > Sitaram Chamarty <sitaramc@gmail.com> 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?
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