From owner-freebsd-hackers Wed Mar 11 18:15:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05953 for freebsd-hackers-outgoing; Wed, 11 Mar 1998 18:15:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05883; Wed, 11 Mar 1998 18:15:23 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id UAA25351; Wed, 11 Mar 1998 20:15:22 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 11 Mar 1998 20:15:17 -0600 To: ctm-announce@FreeBSD.ORG, stable@FreeBSD.ORG, hackers@FreeBSD.ORG From: Richard Wackerbarth Subject: Last Chance - Proposal to discontinue CTM distribution of FreeBSD-2.1 Cc: jkh@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to hit so many lists, but I think that it is important to make sure that everyone has a chance to complain before it is too late. As far as I can see, the 2.1 branch is either dead, or so near it that I do not think that the weekly delta generation for this branch is worth the effort. If there are any additional changes to the branch, they will still be available by CVSup or can be extracted from your local copy of the CVS tree which is contained on the latest CD's. Since I feel that most users who have not already upgraded to 2.2 are still running 2.1 because, for their purpose, "it ain't broke", I doubt that they are are really interested in updating 2.1. Therefore, this is your final warning. Unless I hear strong opposition, the ctm-src-2_1 list will be terminated and the diskspace on the various mirrors will be released next week. Therefore, if you object, speak up NOW. Richard Wackerbarth CTM-Meister To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message