From owner-freebsd-stable  Fri Nov  8 07:39:34 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA14803
          for stable-outgoing; Fri, 8 Nov 1996 07:39:34 -0800 (PST)
Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14785
          for <stable@FreeBSD.ORG>; Fri, 8 Nov 1996 07:39:30 -0800 (PST)
Received: from [208.2.87.4] (cod [208.2.87.4])
          by eel.dataplex.net (8.7.5/8.7.3) with ESMTP id JAA11000;
          Fri, 8 Nov 1996 09:38:09 -0600 (CST)
X-Sender: rkw@mail.dataplex.net
Message-Id: <l0301060daea903e2acc9@[208.2.87.4]>
In-Reply-To: <10583.847464619@time.cdrom.com>
References: Your message of "Fri, 08 Nov 1996 09:55:51 EST."            
 <Pine.3.89.9611080953.A19812-0100000@solar.os.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 8 Nov 1996 09:36:53 -0600
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
From: Richard Wackerbarth <rkw@dataplex.net>
Subject: Re: The curtain is going down on 2.1-stable in 5 days!
Cc: stable@FreeBSD.ORG
Sender: owner-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> Thanks for the "heads-up."  What is the proper method for keeping a
>> 2.1.5-RELEASE kernel up to date?  Is it 2.1-STABLE (via sup) until the 12th
>> or is another method recommended?
>
>2.1-stable via CVSup (recommended over sup) or CTM, yes.  Both will be
>maintained right up until the end (and, in the case of the former, for
>some time afterwards since a tag's a tag).

And in the case of the latter, no changes == no mail :-)