From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl Worth Subject: Re: Figured out how to get Mozilla into git Date: Fri, 09 Jun 2006 19:34:27 -0700 Message-ID: <87y7w5lowc.wl%cworth@cworth.org> References: <9e4733910606081917l11354e49q25f0c4aea40618ea@mail.gmail.com> <46a038f90606082006t5c6a5623q4b9cf7b036dad1e5@mail.gmail.com> <46a038f90606091814n1922bf25l94d913238b260296@mail.gmail.com> <9e4733910606091848r5fb4d565taabfc5198140daf2@mail.gmail.com> <9e4733910606091921o1d07826w8292dc22b1872345@mail.gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Jun__9_19:34:21_2006-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Cc: "Linus Torvalds" , "Martin Langhoff" , git X-From: git-owner@vger.kernel.org Sat Jun 10 04:34:50 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 1FotJH-00082A-CE for gcvg-git@gmane.org; Sat, 10 Jun 2006 04:34:47 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932362AbWFJCeo (ORCPT ); Fri, 9 Jun 2006 22:34:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932366AbWFJCeo (ORCPT ); Fri, 9 Jun 2006 22:34:44 -0400 Received: from mx1.redhat.com ([66.187.233.31]:22197 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932362AbWFJCeo (ORCPT ); Fri, 9 Jun 2006 22:34:44 -0400 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k5A2YWsT025058; Fri, 9 Jun 2006 22:34:32 -0400 Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k5A2YV64010891; Fri, 9 Jun 2006 22:34:31 -0400 Received: from raht.cworth.org (sebastian-int.corp.redhat.com [172.16.52.221]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id k5A2YSlQ009119; Fri, 9 Jun 2006 22:34:30 -0400 To: "Jon Smirl" In-Reply-To: <9e4733910606091921o1d07826w8292dc22b1872345@mail.gmail.com> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.4 Mule/5.0 (SAKAKI) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: --pgp-sign-Multipart_Fri_Jun__9_19:34:21_2006-1 Content-Type: text/plain; charset=US-ASCII On Fri, 9 Jun 2006 22:21:17 -0400, "Jon Smirl" wrote: > > Could you clone the repo and delete changesets earlier than 2004? Then > I would clone the small repo and work with it. Later I decide I want > full history, can I pull from a full repository at that point and get > updated? That would need a flag to trigger it since I don't want full > history to come over if I am just getting updates from someone else's > tree that has a full history. This is clearly a desirable feature, and has been requested by several people (including myself) looking to switch some large-ish histories from an existing system to git. If you'd like to look through git archives for some discussion of the issues that would be involved here, look for "shallow clone". There's a related proposal termed "lazy clone" for one that would pull down missing objects as needed over the network. My impression is that both things will eventually be implemented. There's certainly nothing fundamental in git that will prevent them, (though there will be some interesting things to resolve as a real patch for this stuff is explored). -Carl --pgp-sign-Multipart_Fri_Jun__9_19:34:21_2006-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEii+z6JDdNq8qSWgRApRLAKCKvSCqBavB4keeGb1TqoWBqJZD+QCgkoAy 4TDra9XoQXSjhzP2odltGPk= =cBSC -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Jun__9_19:34:21_2006-1--