From owner-freebsd-current Tue Nov 17 13:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19391 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:36:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heaven.gigo.com (ppp.gigo.com [207.173.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19385 for ; Tue, 17 Nov 1998 13:36:39 -0800 (PST) (envelope-from jfesler@gigo.com) Received: by heaven.gigo.com (8.8.8/8.8.8) with SMTP id NAA07157 for ; Tue, 17 Nov 1998 13:36:03 -0800 (PST) X-SMTP: helo heaven.gigo.com from jfesler@gigo.com server jfesler@heaven.gigo.com ip 207.173.133.57 Date: Tue, 17 Nov 1998 13:36:01 -0800 (PST) From: Jason Fesler To: current@FreeBSD.ORG Subject: Heads up file Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, this may seem a bit strange for you, but here's a stab at a possible solution for people who can't keep up with the sheer bulk of -current. Maintain a README type file, perhaps called HEADSUP, with warnings and announcements in reverse cronological order, and dated. I did this for a couple of the software projects I've done in the past, and it was extremely helpful. People only had to read down to the point where they last upgrade, and nothing had to be left out for fear of being overly redudant. Every one in a while the file would be trimmed (roughly yearly) to keep the file size sane, but it overall worked out well. Am I on drugs for suggesting it here? Or just on drugs? :-). Jason Fesler |".. and ten thousand noblemen squated and Price, Speed, Quality - | strained, for the King's word, was law." Pick any two. | - SCA Folklore To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message