From owner-freebsd-current Sun Dec 8 16:04:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA01701 for current-outgoing; Sun, 8 Dec 1996 16:04:07 -0800 (PST) Received: from broon.off.connect.com.au (broon.off.connect.com.au [203.63.69.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA01691 for ; Sun, 8 Dec 1996 16:04:03 -0800 (PST) Received: from connect.com.au (ggm@localhost) by broon.off.connect.com.au with ESMTP id KAA14361 (8.7.6h/IDA-1.6 for ); Mon, 9 Dec 1996 10:03:19 +1000 (EST) X-Authentication-Warning: broon.off.connect.com.au: ggm owned process doing -bs X-Mailer: exmh version 1.6.9 8/22/96 To: freebsd-current@freebsd.org Subject: siguing into current from a random version In-reply-to: Your message of "Sun, 08 Dec 1996 17:31:25 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 10:03:18 +1000 Message-ID: <14360.850089798@connect.com.au> From: George Michaelson Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. -George -- George Michaelson | connect.com.au pty/ltd Email: ggm@connect.com.au | c/o AAPT, Phone: +61 7 3834 9976 | level 8, the Riverside Centre, Fax: +61 7 3834 9908 | 123 Eagle St, Brisbane QLD 4000