From owner-freebsd-hackers Sat Sep 27 15:31:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16495 for hackers-outgoing; Sat, 27 Sep 1997 15:31:16 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16490 for ; Sat, 27 Sep 1997 15:31:12 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id QAA01063; Sat, 27 Sep 1997 16:30:34 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA27837; Sat, 27 Sep 1997 16:30:30 -0600 (MDT) Date: Sat, 27 Sep 1997 16:30:30 -0600 (MDT) Message-Id: <199709272230.QAA27837@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Nate Williams , Chuck Robey , Eivind Eklund , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: <19970927220550.60658@bitbox.follo.net> References: <199709271529.RAA11811@bitbox.follo.net> <19970927191524.23340@bitbox.follo.net> <199709271930.NAA27312@rocky.mt.sri.com> <19970927220550.60658@bitbox.follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > In what way are release tags expensive? > > > > > > > > I'm not sure exactly what Jordan was referring to, but I know that every > > > > time the tree gets tagged, a huge ctm delta is generated. I think this > > > > would mean a lot of net traffic also for folks using cvsup. > > All files are modified when tags are put down, so it means CTM deltas > > and CVS deltas are rather large, although the change for each file is > > rather small. > > This only happens if all files are tagged, AFAIK? Yes. > I was referring to > adding tags to those files that actually are modified, to tie each > commit and each merge together so it can be viewed as a single change > at a later point in time, instead of being viewed as one change for > each file, with no usable way to automatically find out what other > changes was done at the same time. Well, this is supposed to be how it's done, but CVS doesn't keep track of a single 'commit' in this manner. Other VC software does (such as P3). > This do not require modifying all > untouched files unless I've totally misunderstood the way RCS tags work. But, it's the way CVS works. And, forcing people to install X different versions of the software (where A is the base revision, and you need to apply a number of 'delta' revisions to take you up to each SNAP/RELEASE') is not a workable solution either. Nate