From owner-freebsd-stable Wed Mar 15 12:15:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 209B637B9BE for ; Wed, 15 Mar 2000 12:15:36 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p47-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.112]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA07754; Thu, 16 Mar 2000 05:12:48 +0900 (JST) Message-ID: <38CFEE6B.83B61812@newsguy.com> Date: Thu, 16 Mar 2000 05:11:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mark Ovens Cc: Sheldon Hearn , bwoods2@uswest.net, freebsd-stable@FreeBSD.ORG Subject: Re: RELENG_4 References: <2164.953047401@axl.ops.uunet.co.za> <20000314183713.C239@parish> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > > So does this mean that I should change the tag in my supfile to > RELENG_4 from ``.'' now if I want to (ultimately) track 4.x-STABLE > rather than 5.x-CURRENT? There are new 4.x-stable-supfile and 4.x-secure-stable-supfile files. Since the plan up to the last moment, as far as I knew (and I had asked), was to keep 4.x -current for a while longer, one can assume that 3.x will not be cease to be the prefered "stable" platform for a while. As a matter of fact, we don't even have an automated source upgrade procedure to 4.0 from 3.x-stable yet. "Make upgrade" won't work, and neither will a simple "make world", and the path that exists to do so is not the kind of thing we usually ask of -stable users. Anyway, these files have been committed to RELENG_3, RELENG_4 and -current. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message