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

From: seventh guardian <seventhguardian@gmail.com>
Date: Apr 6, 2008, 18:06 UTC
Message-ID: <1caff7430804061106m49a60bc0wbbd9001394e83589@mail.gmail.com>
In-Reply-To: <20080406175136.GB32399@coredump.intra.peff.net>

On Sun, Apr 6, 2008 at 6:51 PM, Jeff King <peff@peff.net> wrote:

Show 5 quoted lines

> On Sun, Apr 06, 2008 at 06:11:12PM +0100, seventh guardian wrote:
>
>  Hmm. This _should_ just work, but something funny is going on. For some
>  reason the "local master" is telling us that his HEAD points to
>  f7a51afd, but we don't actually get that object.

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).

Show 5 quoted lines

>  But I'm not quite sure
>  how we get into that situation; my guess is that there is something
>  confusing going on at the remote master, since the http fetching code is
>  not as strict and might fail to notice a missing object there. Is it
>  possible for us to see the remote master so we can take a look?

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... ;)

 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/

On the other hand, I don't have this issue with this repo, which doesn't have any local commit:

git://anongit.freedesktop.org/git/mesa/drm/

Now that I look at the addresses, the "nouveau" part is common to the problematic repo's. I'll make a local change on the last repo and see if it also exhibits the problem. I'll report back ASAP.

Cheers,
  Renato