Date: Mon, 29 Aug 2011 22:41:51 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: "K. Macy" <kmacy@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: Official git export Message-ID: <alpine.GSO.1.10.1108292239460.1411@multics.mit.edu> In-Reply-To: <CAHM0Q_N-JapN_7H_%2B59kLkwo0jb-H4LcAe48jyuLAtJkCEK_1Q@mail.gmail.com> References: <35765857-1314243257-cardhu_decombobulator_blackberry.rim.net-329610575-@b2.c15.bise7.blackberry> <CAJ-Vmo=v0UkQarauKrvWKdjMTC81BwXmyhU__rnaQeL3z45L-g@mail.gmail.com> <slrnj5ddgp.4ck.vadim_nuclight@kernblitz.nuclight.avtf.net> <CAMBSHm8uX45k0M4on=5Cpw_CKoddA=4oJSNXpH7dGPt=Vy2HOw@mail.gmail.com> <alpine.BSF.2.00.1108261000040.48200@fledge.watson.org> <slrnj5lc58.jd1.vadim_nuclight@kernblitz.nuclight.avtf.net> <4e5ba9c3.bzHIw1KEy8R2QcK7%perryh@pluto.rain.com> <3420B331-C697-468A-80BA-B31C33804710@freebsd.org> <4e5c5b5f.moT7dLemOuteQJ5T%perryh@pluto.rain.com> <4E5C364D.7070904@freebsd.org> <CAHM0Q_Mq3YEEpB6uNymjtd=WCQuTR6gd=71EsLxJf5J0ygyjiw@mail.gmail.com> <alpine.GSO.1.10.1108292220110.1411@multics.mit.edu> <CAHM0Q_N-JapN_7H_%2B59kLkwo0jb-H4LcAe48jyuLAtJkCEK_1Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1108292239460.1411>