From owner-freebsd-hackers Sat Sep 27 15:55:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18220 for hackers-outgoing; Sat, 27 Sep 1997 15:55:23 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18215 for ; Sat, 27 Sep 1997 15:55:16 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id PAA13668; Sat, 27 Sep 1997 15:54:42 -0700 (MST) From: Terry Lambert Message-Id: <199709272254.PAA13668@usr03.primenet.com> Subject: Re: How do I check out a snapshot? To: eivind@bitbox.follo.net (Eivind Eklund) Date: Sat, 27 Sep 1997 22:54:41 +0000 (GMT) Cc: nate@mt.sri.com, chuckr@glue.umd.edu, perhaps@yes.no, jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <19970927220550.60658@bitbox.follo.net> from "Eivind Eklund" at Sep 27, 97 10:05:50 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This only happens if all files are tagged, AFAIK? 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. This do not require modifying all > untouched files unless I've totally misunderstood the way RCS tags work. Plus you could have a change comment to go with the tag. And you could put it all in "CVS unlock" after you are done with your writer lock. Just like we did at Novell with CVS starting in 1993. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.