From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin Langhoff" Subject: Re: Delta-transfer using thin-pack Date: Tue, 21 Feb 2006 15:05:23 +1300 Message-ID: <46a038f90602201805l481af8ddl5b2d30862f61e29@mail.gmail.com> References: <7voe13exoq.fsf@assigned-by-dhcp.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: git@vger.kernel.org X-From: git-owner@vger.kernel.org Tue Feb 21 03:05:31 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FBMu9-0005dM-52 for gcvg-git@gmane.org; Tue, 21 Feb 2006 03:05:29 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161274AbWBUCFY (ORCPT ); Mon, 20 Feb 2006 21:05:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161275AbWBUCFY (ORCPT ); Mon, 20 Feb 2006 21:05:24 -0500 Received: from wproxy.gmail.com ([64.233.184.193]:56153 "EHLO wproxy.gmail.com") by vger.kernel.org with ESMTP id S1161274AbWBUCFY convert rfc822-to-8bit (ORCPT ); Mon, 20 Feb 2006 21:05:24 -0500 Received: by wproxy.gmail.com with SMTP id i22so1009551wra for ; Mon, 20 Feb 2006 18:05:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r1fxlr8rVMgSwmMz0sVdoJcY2rFM2XTN7hnxSEaSD1/I0HWxdaqm6LDsDdTkG0QAX7GTkOp/0H1MO0nrUtd9l13SDoZ0drhH7Hpl4pAWiREsw0xxBy8EmU6LUb9TbaMkL9NDmoWsKJ6onQPhd08N+agD8cw1YjuJojgZXGYYWqE= Received: by 10.54.67.15 with SMTP id p15mr11345wra; Mon, 20 Feb 2006 18:05:23 -0800 (PST) Received: by 10.54.127.9 with HTTP; Mon, 20 Feb 2006 18:05:23 -0800 (PST) To: "Junio C Hamano" In-Reply-To: <7voe13exoq.fsf@assigned-by-dhcp.cox.net> Content-Disposition: inline Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On 2/20/06, Junio C Hamano wrote: > I'll be sending out three experimental patches that would come > on top of "next". With them, you should be able to: I see that an updated version of this has made it to next & pu. Cool stuff -- fetched, made, and playing w it ;-) m