From owner-freebsd-current Thu Oct 8 17:04:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24426 for freebsd-current-outgoing; Thu, 8 Oct 1998 17:04:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24370 for ; Thu, 8 Oct 1998 17:04:00 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA03261; Thu, 8 Oct 1998 17:03:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: Is tickadj still required in -CURRENT ? In-reply-to: Your message of "Thu, 08 Oct 1998 17:37:41 EDT." Date: Thu, 08 Oct 1998 17:03:43 -0700 Message-ID: <3256.907891423@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 8 Oct 1998, John Polstra wrote: > > > In any case, given that a code freeze is in effect, > > You're kidding. Since when? It's been more of a code slush, and the rule still nonetheless in effect seems to be "bring it in if it's not too scarey OR if it represents something we really need to get out of the way before 3.0, or it will be more painful after." That still leaves a large number of things which are being deliberately postponed until after 3.0. They'd be nice to have, but we don't have an urgent need to cross the bridges they represent at this particular time. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message