From owner-freebsd-current Thu Jan 21 22:01:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23945 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:01:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daphne.bogus (dialup34.black-hole.com [206.145.13.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23934 for ; Thu, 21 Jan 1999 22:00:46 -0800 (PST) (envelope-from hank@black-hole.com) Received: from localhost (hank@localhost) by daphne.bogus (8.9.1/8.8.8) with SMTP id XAA59405 for ; Thu, 21 Jan 1999 23:42:20 -0600 (CST) (envelope-from hank@black-hole.com) X-Authentication-Warning: daphne.bogus: hank owned process doing -bs Date: Thu, 21 Jan 1999 23:42:20 -0600 (CST) From: Henry Miller X-Sender: hank@daphne.bogus cc: current@FreeBSD.ORG Subject: Re: CVS tags to use? In-Reply-To: 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 On Thu, 21 Jan 1999, Jaye Mathisen wrote: > > The readme in /usr/share/examples hasn't been updated in a while... > > WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x > branch). > > Right now, I have tag=., and I can't get a compilable kernel to save my > life, problems in syscons. RELENG_3 Related to the above question though, is when should I drop my subscription to current, and move to stable (the mailing lists) I presume that for a while the current mailing list will be more relavent as people on it will at least remember similear problems, while the -stable list will have 2.2.x users who have never seen our porblems. Gradually this would change though, as the 4.x path moves beyond the 3.x track in significant ways. (Already a couple important changes are in the 4.x track) I guess the big questions is where do I look for 3.x Head-up messages. -- http://www.black-hole.com/users/henrymiller/ hank@black-hole.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message