From owner-freebsd-questions Sat Aug 25 8: 7:27 2001 Delivered-To: freebsd-questions@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 942F237B40E; Sat, 25 Aug 2001 08:07:21 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.11.6/8.11.5) id f7PF7Io68637; Sat, 25 Aug 2001 10:07:18 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010825175631.C559@ringworld.oblivion.bg> Date: Sat, 25 Aug 2001 10:07:18 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Peter Pentchev Subject: Re: cvsup RELENG_4 = 4.4-RC1 ? Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Chojin Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 25-Aug-2001 Peter Pentchev wrote: > On Sat, Aug 25, 2001 at 09:45:41AM -0500, Conrad Sabatier wrote: >> >> On 25-Aug-2001 Chojin wrote: >> > Hello, >> > >> > I want to know if RELENG_4 will download 4.4-RC1 or lastest 4.3-STABLE >> > files >> > ? >> > Because I don't want to be in 4.4-RC1, too many problems. >> >> Then you don't want to cvsup RELENG_4, I guess. >> >> More problems in 4.3-STABLE than in RC, actually. > > Hrm.. I thought Warner fixed some things in the PCI BIOS handling, > Eric Melville fixed up some sysinstall issues, others MFC'd other > important fixes.. What exactly are you referring to - problems that > were introduced *since* 4.4-RC1? If so, what are those? Perhaps I wasn't clear enough here. I meant that he'd be better off with the release candidate than with an earlier stable. -- Conrad Sabatier conrads@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message