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. :) > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
