From owner-freebsd-hackers Thu Feb 2 15:39:39 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA20918 for hackers-outgoing; Thu, 2 Feb 1995 15:39:39 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id PAA20912 for ; Thu, 2 Feb 1995 15:39:38 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA15211; Thu, 2 Feb 95 16:33:40 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502022333.AA15211@cs.weber.edu> Subject: Re: Source Tree Ettiquite (was Re: sup: Ok, I'm gonna do it.) To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Thu, 2 Feb 95 16:33:39 MST Cc: hackers@FreeBSD.org In-Reply-To: <9502022322.AA22056@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Feb 2, 95 06:22:34 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > < > > Thus we are left with CVS + 1 snapshot, rather than CVS + 2(3) snapshots. > > Which is still more disk than I have available to me for this > purpose. This is for the distribution site, and the site where the release engineering is done (if different). Programmers working on pieces of the whole only check out the parts they are going to work on from a remotely accessed tree. How do you handle this now? You either have the whole tree locally or you do not. In which case the partial tree checkout techniques still apply. Checking things into a source repository makes no sense unless you expect a conflict with someone else, or expect to need to share a common source base with someone else. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.