From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Shawn O. Pearce" Subject: Re: Bad objects error since upgrading GitHub servers to 1.6.1 Date: Tue, 27 Jan 2009 19:57:03 -0800 Message-ID: <20090128035703.GG1321@spearce.org> References: <7v1vuo1f6d.fsf@gitster.siamese.dyndns.org> <7vvds0z1c1.fsf@gitster.siamese.dyndns.org> <7vk58gz04l.fsf@gitster.siamese.dyndns.org> <7vfxj4yzjj.fsf@gitster.siamese.dyndns.org> <20090128020220.GE1321@spearce.org> <7v3af4yvmu.fsf@gitster.siamese.dyndns.org> <20090128033020.GF1321@spearce.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org To: Stephen Bannasch X-From: git-owner@vger.kernel.org Wed Jan 28 04:58:33 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LS1ZP-000609-Pg for gcvg-git-2@gmane.org; Wed, 28 Jan 2009 04:58:32 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752418AbZA1D5H (ORCPT ); Tue, 27 Jan 2009 22:57:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752390AbZA1D5F (ORCPT ); Tue, 27 Jan 2009 22:57:05 -0500 Received: from george.spearce.org ([209.20.77.23]:47054 "EHLO george.spearce.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752346AbZA1D5E (ORCPT ); Tue, 27 Jan 2009 22:57:04 -0500 Received: by george.spearce.org (Postfix, from userid 1001) id 356C038210; Wed, 28 Jan 2009 03:57:03 +0000 (UTC) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Stephen Bannasch wrote: > At 7:30 PM -0800 1/27/09, Shawn O. Pearce wrote: >> PJ - the short story here is, to forever work around these buggy >> 1.6.1 clients, you'd have to either run an old server forever, >> or forever run a patched server that disables the newer ".have" >> extension in the advertised data written by git-upload-pack. >> There just isn't a way to hide this from the client. >> >> Really though, I'd recommend getting your users to upgrade to a >> non-buggy client. Pasky has the same problem on repo.or.cz; if >> he doesn't have it already he will soon when he upgrades... > > Do you know if this problem is fixed in tag v1.6.1.1? > > Tagger: Junio C Hamano > Date: Sun Jan 25 12:41:48 2009 -0800 > commit 5c415311f743ccb11a50f350ff1c385778f049d6 Without even checking Git I can tell you it isn't fixed by 1.6.1.1. The date on the tag is Jan 25th, 2 full days before PJ reported the problem and a solution was proposed... -- Shawn.