From owner-freebsd-current Sun Dec 8 17:03:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA04986 for current-outgoing; Sun, 8 Dec 1996 17:03:20 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA04981 for ; Sun, 8 Dec 1996 17:03:17 -0800 (PST) Received: from downlink.eng.umd.edu (downlink.eng.umd.edu [129.2.98.182]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id UAA01378; Sun, 8 Dec 1996 20:03:13 -0500 (EST) Received: from localhost (chuckr@localhost) by downlink.eng.umd.edu (8.8.3/8.7.3) with SMTP id UAA10151; Sun, 8 Dec 1996 20:03:13 -0500 (EST) X-Authentication-Warning: downlink.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 8 Dec 1996 20:03:12 -0500 (EST) From: Chuck Robey X-Sender: chuckr@downlink.eng.umd.edu To: George Michaelson cc: freebsd-current@freebsd.org Subject: Re: siguing into current from a random version In-Reply-To: <14360.850089798@connect.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996, George Michaelson wrote: > > > I've come into FreeBSD after 2+ years tracking NetBSD. I'm still a bit > confused about some procedures. > > NetBSD has a summary of CVS changes and a rolling README of current state > changes similar to RLOG lines from RCS. Does FreeBSD have this kind of > summary of changes under CVS? The individual CVS update reports are vital > for some people, but for passive drones like me, less useful than something > like a ChangeLog which is append-grown. > > The re-sync to current process is not clear. NetBSD ususally had an indication > from known people when re-sync was vital, and irregular checkpoint tarsets > existed for people who were nervous of the in-place libc.so upgrade etc etc. I've never tracked NetBSD, so I'm not sure, but I think maybe that CVSROOT/commitlogs, which has the commit logs broken up by top level directories, has what you're asking for, a log of all commits made. We don't explicitly make tars when things change, probably because those changes are often accompanied by a short period of some level of broken-ness, while bugs are found. Instead, we have snaps, for those who don't want to track current totally, but who want to stay reasonably close, and contribute error reports. Snaps are usually done during periods of relative stability, so maybe that's what you're asking for? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------