From owner-freebsd-current  Mon Feb 24 11:52:57 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA12145
          for current-outgoing; Mon, 24 Feb 1997 11:52:57 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA12134
          for <freebsd-current@FreeBSD.ORG>; Mon, 24 Feb 1997 11:52:52 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id MAA10821; Mon, 24 Feb 1997 12:51:26 -0800 (PST)
Message-ID: <XFMail.970224125126.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSI.3.94.970217163536.9200C-100000@militzer.me.tuns.ca>
Date: Mon, 17 Feb 1997 15:05:30 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: Antonio Bemfica <bemfica@militzer.me.tuns.ca>
Subject: RE: downgrading from current
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi Antonio Bemfica;  On 17-Feb-97 you wrote: 
> Half of the machines around here are running 2.1.6 and the other half are
> running -current.  A couple of the -current machines are now being used
> for tasks that require a bit more stability than -current provides, and I
> was wondering if bringing them down from -current would be a bad move. 
> 
> I am also wondering how to accomplish that (maybe using RELENG_2_2 as the
> tag on the cvsup file would do it?).  I'd still have some -current
> machines to play with, and I'd have a machine running 2.2 (BETA) to get
> ready for an upgrade for the other ones.  Any comments or suggestions? I'd
> appreciate some guidance. 

I found myself in the same place.  Only with one machine to compile on. 
This experience is reflected in some notes I am posting here.  So far
nothing major, but some discrepencies do exist.

Simon