From owner-freebsd-stable Sat Nov 9 05:32:15 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA26789 for stable-outgoing; Sat, 9 Nov 1996 05:32:15 -0800 (PST) Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA26782 for ; Sat, 9 Nov 1996 05:32:11 -0800 (PST) Received: from baloon.mimi.com (sjx-ca34-11.ix.netcom.com [204.31.236.107]) by dfw-ix10.ix.netcom.com (8.6.13/8.6.12) with ESMTP id FAA03075; Sat, 9 Nov 1996 05:31:39 -0800 Received: (from asami@localhost) by baloon.mimi.com (8.8.2/8.6.12) id FAA11567; Sat, 9 Nov 1996 05:31:37 -0800 (PST) Date: Sat, 9 Nov 1996 05:31:37 -0800 (PST) Message-Id: <199611091331.FAA11567@baloon.mimi.com> To: jkh@time.cdrom.com CC: stable@freebsd.org In-reply-to: <10472.847447745@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: The curtain is going down on 2.1-stable in 5 days! From: asami@freebsd.org (Satoshi Asami) Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * So. David and I have decided that next Tuesday, the 12th of November, * would be an excellent time to start putting FreeBSD 2.1.6 to bed, and * if you've got any critical bug fixes or security problems to report in * 2.1-stable, now would be an excellent time to raise them before it's * too late. I will put in the latest bsd.port.mk (there should not be any difference between -current and -stable) before that, but it will likely change again. Is it ok to swap it right before the release? Satoshi