Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:35258 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759883Ab0HEIqT (ORCPT ); Thu, 5 Aug 2010 04:46:19 -0400 Date: Thu, 05 Aug 2010 01:46:37 -0700 (PDT) Message-Id: <20100805.014637.13722703.davem@davemloft.net> To: arnd@arndnet.de Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org, sfr@canb.auug.org.au Subject: Re: GIT: net-*2.6 rebased... From: David Miller In-Reply-To: <4C5A6EFE.7040703@arndnet.de> References: <20100804.162141.15218463.davem@davemloft.net> <4C5A6EFE.7040703@arndnet.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Arnd Hannemann Date: Thu, 05 Aug 2010 09:57:50 +0200 > if I try to fetch from net-next-2.6, I get: > fatal: The remote end hung up unexpectedly > > if I try to clone net-2.6: > (e.g. git clone git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git > > I get lots of errors reading the tags "does not point to a valid object!" and then: > remote: error: Could not read 3cfc2c42c1cbc8e238bb9c0612c0df4565e3a8b4 > remote: fatal: Failed to traverse parents of commit 7aaaaa1e44b2a4047dfe05f304a5090eb995cf44 > remote: aborting due to possible repository corruption on the remote side. > fatal: early EOF > fatal: index-pack failed Hmmm, since I can I tried an ssh based clone and it works. But indeed if I try to use the git:// URL it fails. Oh I see, the alternates files in those repos are completely broken. They have: /home/davem/git/../torvalds/linux-2.6.git/objects /home/davem/git is a symlink to /pub/scm/linux/kernel/git/davem so if I login and "cd git" then: git clone --shared --bare ../torvalds/linux-2.6.git net-next-2.6.git which is how I always create my trees, we get that unusable 'alternates' path above. The ".." works when my GIT directory is the working directory, but not as part of the symlink include path to get there. I fixed the alternates file but it will take some time for the fix to propagate from master.kernel.org Let me know if it doesn't work even after an hour or so. Thanks.