From owner-freebsd-stable Tue Sep 1 18:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04914 for freebsd-stable-outgoing; Tue, 1 Sep 1998 18:19:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lafcol (lafcol.lafayette.edu [139.147.8.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA04896 for ; Tue, 1 Sep 1998 18:18:59 -0700 (PDT) (envelope-from knollm@lafcol.lafayette.edu) Received: from localhost by lafcol (SMI-8.6/SMI-SVR4) id VAA23388; Tue, 1 Sep 1998 21:16:13 -0400 Date: Tue, 1 Sep 1998 21:16:12 -0400 (EDT) From: Mike Knoll To: "Jordan K. Hubbard" cc: Ron Echeverri , stable@FreeBSD.ORG Subject: Re: Requisite steps for tracking -stable In-Reply-To: <4042.904690902@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I track -stable, and am "limitedly" interested in it. I try to keep up with it, but school and work sometimes halt all efforts. I have found myself several times without an answer to compile problems in -stable. I was recently introduced to the version comments cvsup keeps(http://www.freebsd.org/cgi/cvsweb.cgi). I was wondering, after cvsup'ing, is there anyway to get that information emailed, or stored on only those files that have changed? So, I get that information mailed to me after I cvsup, including all new changes. I think that would be a great way to track -stable. I could read all about the little changes. Also, maybe those comments could scream at you more if it's a critical change that needs attention, like messages that require attention before 'make buildworld'ing. Just my thoughts, not sure on the capablity of this, feel free to shoot it down. On Tue, 1 Sep 1998, Jordan K. Hubbard wrote: > > So, to make things as clear as possible, what are all the requisite > > steps? I, too, was under the impression subscribing to freebsd-stable > > would be enough to keep track of vital information regarding the > > -stable tree. If there is something else that must be done, this > > should be detailed somewhere obvious, like the Handbook. > > I think it's basically "read -stable if you track stable, read > -current if you track -current" - we just need to get people to make > important announcements to them with a bit more reliability and I think > that'll happen now in the future. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message