From owner-freebsd-arch@FreeBSD.ORG Tue Aug 30 02:41:55 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 1AD7D106564A; Tue, 30 Aug 2011 02:41:55 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id 655C38FC08; Tue, 30 Aug 2011 02:41:54 +0000 (UTC) X-AuditID: 12074422-b7ba7ae000000a14-3a-4e5c4debe585 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id BD.89.02580.BED4C5E4; Mon, 29 Aug 2011 22:41:47 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id p7U2frLa022832; Mon, 29 Aug 2011 22:41:53 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p7U2fqjN015316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Aug 2011 22:41:53 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id p7U2fpBM024488; Mon, 29 Aug 2011 22:41:51 -0400 (EDT) Date: Mon, 29 Aug 2011 22:41:51 -0400 (EDT) From: Benjamin Kaduk To: "K. Macy" In-Reply-To: Message-ID: 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> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-38367664-1314672111=:1411" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgleLIzCtJLcpLzFFi42IR4hTV1n3tG+NnMOmKicXs6dOYLB7v3cLm wOQx49N8lgDGKC6blNSczLLUIn27BK6M/ct3sxfc4qvoWb2HrYHxHXcXIyeHhICJxPrOd8wQ tpjEhXvr2boYuTiEBPYxSsy9PpURwtkA5Lx/xAThHGCSOLx2AzuE08Ao0f15PztIP4uAtsS0 LVPZQGw2ARWJmW82gtkiAooSJ/6uAKrh4GAWkJGY89obJCwsoCDxv3M72GpOgUCJRe1fwWxe AQeJYzPOs0LMX8QmceTUdbCEqICOxOr9U1ggigQlTs58AmYzC/hJdO34zDaBUXAWktQsJKlZ YKutJZ6dt4AIa0vcv9nGtoCRZRWjbEpulW5uYmZOcWqybnFyYl5eapGuqV5uZoleakrpJkZQ QLO7KO1g/HlQ6RCjAAejEg/vh3PRfkKsiWXFlbmHGCU5mJREeR/5xPgJ8SXlp1RmJBZnxBeV 5qQWH2KU4GBWEuG9oQaU401JrKxKLcqHSUlzsCiJ83LtdPATEkhPLEnNTk0tSC2CycpwcChJ 8CYAI1dIsCg1PbUiLTOnBCHNxMEJMpwHaHgESA1vcUFibnFmOkT+FKOilDhvGkhCACSRUZoH 1wtLOK8YxYFeEYZo5wEmK7juV0CDmYAGXzKMBhlckoiQkmpgTD+71zWnOVVKfFWN0cOKjxM2 v77/4H8U6yk/fUFbUbHT3sWs+bpT9fr+iSzNs5zZfXynsXdpxjSu3GKp7zt/hOuW+QXyuV0z i7SbzdK+yNLx0IxdD52P/Ji0pSwzRC1I/uAlGe47sh/kGRjDvHZd0Xt+Sb1/2buS258bhA0t e2OtG9ojF55UYinOSDTUYi4qTgQAK1hmsBMDAAA= 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 02:41:55 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-38367664-1314672111=:1411 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 30 Aug 2011, K. Macy wrote: >> My understanding is that with git it's possible to "graft" one tree onto >> 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 proposed= in >> the context of the net-im/zephyr upstream, where development happened >> concurrently in multiple trees (in different VCSes) for a period of time >> maybe ten years ago. =A0Current development is all consolidated in a sin= gle >> subversion tree, and the proposal was to convert that repository now to = have >> something to work with, and worry about getting the ancient history righ= t 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=20 committing to and pushing from (though I have not really used it, myself,= =20 so could be mistaken). > 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,= =20 and it doesn't really feel like it would be appropriate for splitting up=20 things within base. (It would, however, make some amount of sense if we=20 were ever crazy enough to combine two or more of base, doc/www, and=20 ports.) -Ben ---559023410-38367664-1314672111=:1411--