From owner-freebsd-current Sat Sep 16 13:40:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA17232 for current-outgoing; Sat, 16 Sep 1995 13:40:49 -0700 Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA17202 for ; Sat, 16 Sep 1995 13:40:43 -0700 Received: from [199.183.109.242] by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Sat, 16 Sep 1995 15:40:35 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 16 Sep 1995 15:40:37 -0500 To: "Rodney W. Grimes" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Which SUP files are available and where ? Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk At 2:50 PM 9/16/95, Rodney W. Grimes wrote: >This can still be made to work, just change the name from ``stable'' to >``stable-2.2'' in the sup control files when that tree gets created ( >I suggest YAST (Yet Another Source Tree) for this, as it might be nice >to have critical bug fixes go to users via sup who are running 2.1R, >just cut the cvs and sup updates down to once every 3 days or something >slightly more reasonable for a maintainence mode tree. Why bother with "stable" anything. Just call the tree 2.1, 2.2, 2.3, etc. As for the long term support, I think we should consider CTM as the distribution mechanism rather than sup. Comments? ---- Richard Wackerbarth rkw@dataplex.net