From owner-freebsd-current Fri Jan 5 15:37:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA11071 for current-outgoing; Fri, 5 Jan 1996 15:37:49 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA11058 for ; Fri, 5 Jan 1996 15:37:42 -0800 (PST) Received: from critter.tfs.com ([193.88.44.194]) by ra.dkuug.dk (8.6.12/8.6.12) with ESMTP id AAA25661; Sat, 6 Jan 1996 00:36:16 +0100 Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id AAA00600; Sat, 6 Jan 1996 00:37:38 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: Current is looking more stable these days..? In-reply-to: Your message of "Fri, 05 Jan 1996 15:02:15 PST." <10406.820882935@time.cdrom.com> Date: Sat, 06 Jan 1996 00:37:37 +0100 Message-ID: <598.820885057@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > In contravention of all reason, I've been running it on my gateway box > lately and, as of this morning's sup, things look pretty reasonable > (at least from the perspective of an EISA/ISA box with a 1542CF > controller). > > What do -current folk think about a 2.2-SNAP pretty soon here? Would > you like a grace period of a week or so to tidy up first? Longer? I think I need to kill the bug that I'm tracking in the bmap code, but that should be done by sun evening my time. At least it will be circumvented. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.