From owner-freebsd-stable Sat Dec 19 23:48:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14149 for freebsd-stable-outgoing; Sat, 19 Dec 1998 23:48:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14140 for ; Sat, 19 Dec 1998 23:48:35 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zrdbL-0001B7-00; Sat, 19 Dec 1998 23:48:31 -0800 Date: Sat, 19 Dec 1998 23:48:27 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Lomag cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0-STABLE In-Reply-To: <367C5978.B1242AD4@lomag.net> 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 On Sat, 19 Dec 1998, Lomag wrote: > Can someone please cue me in as when 3.0-stablr branch > will be ready? I'm forced to use 3.0-current and its > very unstable, stays up for about 10 days, after that > things just go haywire. I have to use 3.0 to support > my UW2 scsi card and Seagate Cheetah hard drives. > If anyone can please tell me so I know when to expect > it to upgrade asap. "3.0-stable" is just a name. Basically, the name "3.0-stable" will be given to one of the branches when development on "3.0-current" forks. Questions about 3.0-current should go to the freebsd-current mailing list. Include more detail than "things go haywire", as that won't help anyone fix your problem. Also, 2.2-stable+CAM will also support your UW2 card. > Regards, > Mark Skurzynski > support@lomag.net Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message