From owner-freebsd-stable  Fri Nov  8 07:38:21 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA14491
          for stable-outgoing; Fri, 8 Nov 1996 07:38:21 -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 HAA14475
          for <stable@freebsd.org>; Fri, 8 Nov 1996 07:38:17 -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 JAA10997;
          Fri, 8 Nov 1996 09:38:08 -0600 (CST)
X-Sender: rkw@mail.dataplex.net
Message-Id: <l0301060caea9034788ad@[208.2.87.4]>
In-Reply-To: <Pine.3.89.9611080953.A19812-0100000@solar.os.com>
References: <10472.847447745@time.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 8 Nov 1996 09:35:27 -0600
To: Craig Shrimpton <craigs@os.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

Craig Shrimpton <craigs@os.com> writes:

>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?

Yes, use CVSup or CTM to track "-stable" which is the whole generation of
2.1 development.