Re: [bug] git-clone over ssh fails when repository has local commits

From: Jeff King <peff@peff.net>
Date: Apr 6, 2008, 18:17 UTC
Message-ID: <20080406181749.GA2218@coredump.intra.peff.net>
In-Reply-To: <1caff7430804061106m49a60bc0wbbd9001394e83589@mail.gmail.com>

On Sun, Apr 06, 2008 at 07:06:40PM +0100, seventh guardian wrote:

> This object is the correct HEAD, but it is a local commit (I rebase
> all local changes so that they stay "on top" of the original code).

That shouldn't matter to git; it doesn't care at all about where commits were created.

> Sure, I just thought it would confuse more than it would help. I was
> obviously wrong, as I'm actually using git:// instead of http://....
> sorry... ;)

Heh. OK, scratch what I said before then. :)

Show 5 quoted lines

>  I'm experiencing this with both these repo's, as I have committed
> some local changes to them:
> 
> git://anongit.freedesktop.org/git/nouveau/mesa
> git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/

Can you give an exact set of steps to reproduce? There doesn't seem to be anything wrong with those repos, and I was able to do:

  m1$ git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/
  m1$ cd xf86-video-nouveau && echo foo >>COPYING && git commit -a -m foo
  m2$ git clone ssh://m1/path/to/xf86-video-nouveau

So now my guess is when you make local changes, something funny is going on. Can you describe that process in more detail?

-Peff