From owner-freebsd-stable Sun Apr 23 12:56:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id EC31237B517 for ; Sun, 23 Apr 2000 12:56:18 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id NAA70389; Sun, 23 Apr 2000 13:57:05 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sun, 23 Apr 2000 13:57:05 -0600 (CST) From: Ryan Thompson To: Nate Williams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: <200004231947.NAA08296@nomad.yogotech.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Numerous cross-posts and CC's removed Nate Williams wrote to Poul-Henning Kamp: > > > Core should consider reverting the special rules that were originally > > > created with the expectation of major breakage in 5.x back to > > > the set of rules we had for 3.x and 4.x. > > > > I have no idea what special rules you are talking about for 4.x/5.x. > > > > 4.x-stable is a -stable tree and shall be treated as such. > > I was under the impression that 4.x hasn't been designated as the stable > branch (yet). That will happen when 4.1 is released, but until that > happens 3.x is still considered the -stable release. > > Nate Nate, 4.0 is indeed -STABLE. Some (myself included) are simply staying with 3.4 on production machines until a few of the bugs have been shaken out of 4.0 (though there haven't been many!) Therefore, many individuals are recommending a wait until 4.1 before switching to RELENG_4. Virtually yours, - Ryan -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message