From owner-freebsd-arch@FreeBSD.ORG Tue Aug 30 06:41:17 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65B861065675 for ; Tue, 30 Aug 2011 06:41:17 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 12F888FC23 for ; Tue, 30 Aug 2011 06:41:16 +0000 (UTC) Received: by vxh11 with SMTP id 11so6294067vxh.13 for ; Mon, 29 Aug 2011 23:41:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Rul/yK7QskDiRR6IsvfJlC0YZ8sac4dxXWYbRmRWB3U=; b=M2VkVZK87JuwrF/9uVW5VBe3+dP6tdKVF8OQCmy4SIaYGxuUHtmsQwG4D/q4jkrPwX mu+aVTghWLjdc1HFShE3O3rHqvfzadpF8N9y1s0a/K6oQd2Qhp4Nc9S//mMgoPi+c3au 4JUxeBuiLSictWo2eHPX5XQzHqaD/Eibx9qEw= MIME-Version: 1.0 Received: by 10.52.90.37 with SMTP id bt5mr958980vdb.364.1314686476121; Mon, 29 Aug 2011 23:41:16 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.186.163 with HTTP; Mon, 29 Aug 2011 23:41:16 -0700 (PDT) In-Reply-To: References: <35765857-1314243257-cardhu_decombobulator_blackberry.rim.net-329610575-@b2.c15.bise7.blackberry> <4e5ba9c3.bzHIw1KEy8R2QcK7%perryh@pluto.rain.com> <3420B331-C697-468A-80BA-B31C33804710@freebsd.org> <4e5c5b5f.moT7dLemOuteQJ5T%perryh@pluto.rain.com> <4E5C364D.7070904@freebsd.org> Date: Tue, 30 Aug 2011 08:41:16 +0200 X-Google-Sender-Auth: hBNR4MuX9VJJNWOkL5tnLYOIDV8 Message-ID: From: "K. Macy" To: Benjamin Kaduk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-arch@freebsd.org Subject: Re: Official git export X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 06:41:17 -0000 On Tue, Aug 30, 2011 at 4:41 AM, Benjamin Kaduk wrote: > On Tue, 30 Aug 2011, K. Macy wrote: > >>> My understanding is that with git it's possible to "graft" one tree ont= o >>> another, so that most people only have to check out recent history, and >>> can >>> check out a separate ancient history. =A0This has at least been propose= d in >>> the context of the net-im/zephyr upstream, where development happened >>> concurrently in multiple trees (in different VCSes) for a period of tim= e >>> maybe ten years ago. =A0Current development is all consolidated in a si= ngle >>> subversion tree, and the proposal was to convert that repository now to >>> have >>> something to work with, and worry about getting the ancient history rig= ht >>> at >>> a later time. >>> >> >> My knowledge of git is limited but I know that git clone has the >> --depth option for specifying a shallow clone that only goes back N > > I am pretty sure that this results in a repo that is not very useful for > committing to and pushing from (though I have not really used it, myself,= so > could be mistaken). Why would that be the case? The gitorious repository only goes back to 7 but is very useful. The amount of history one needs to work is usually quite limited. >> changesets. Git also has "submodule" which provides some functionality >> for the notion of subprojects which can limit what is enclosed within >> a given repo to some extent. > > True, but the word on the street around here is that it's kind of a hack, > and it doesn't really feel like it would be appropriate for splitting up > things within base. =A0(It would, however, make some amount of sense if w= e > were ever crazy enough to combine two or more of base, doc/www, and ports= .) Looking at the documentation it is also clear that its applicability is limited as you imply above. Using gitlinks for managing mixed repository state is clearly, if not a hackish design. limited in usability and scope. Cheers