From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Bradley Subject: Re: problem with updating a shallow clone via a branch fetch Date: Mon, 28 Feb 2011 20:07:35 -0600 Message-ID: References: <7vtyfng00i.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Tue Mar 01 03:08:13 2011 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PuF0X-0002xw-3u for gcvg-git-2@lo.gmane.org; Tue, 01 Mar 2011 03:08:13 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754700Ab1CACH5 convert rfc822-to-quoted-printable (ORCPT ); Mon, 28 Feb 2011 21:07:57 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:63730 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754406Ab1CACH4 convert rfc822-to-8bit (ORCPT ); Mon, 28 Feb 2011 21:07:56 -0500 Received: by fxm17 with SMTP id 17so4388580fxm.19 for ; Mon, 28 Feb 2011 18:07:55 -0800 (PST) Received: by 10.223.72.15 with SMTP id k15mr7418763faj.54.1298945275163; Mon, 28 Feb 2011 18:07:55 -0800 (PST) Received: by 10.223.72.208 with HTTP; Mon, 28 Feb 2011 18:07:35 -0800 (PST) In-Reply-To: <7vtyfng00i.fsf@alter.siamese.dyndns.org> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Junio, Thanks for the assistance. I'll be looking in the direction of what could have caused sanity problems in the upstream repo. If it happens again and we can collect more tea leaves (this checkout was cleaned up before I could get a copy of it to do further diagnosis :-/) I'll see what else we can find out. Rick On Mon, Feb 28, 2011 at 6:25 PM, Junio C Hamano wro= te: > Rick Bradley writes: > >> So I have a git repo that is shallow cloned: >> >> =A0 % git clone --depth 1 >> >> Sometimes (very rarely), when I do a branch fetch to update that >> repository I get an error: >> >> =A0% git fetch origin +refs/head/:refs/remotes/origin/ >> >> fatal: did not find object for shallow > > The message comes from the repository you are fetching from. =A0When = you > fetch from a shallow clone, the fetch process on your end tells the o= ther > side what commits your incomplete history ends at, and if the other e= nd > does not have any of these commits, you get that message. =A0So the o= nly > case (unless there is a bug---and I don't think this codepath is heav= ily > exercised so it is very possible there are bugs) you would see that > message is if the other side rewound the branch and then later garbag= e > collection lost the commit. >