From owner-freebsd-current Thu Jun 20 06:55:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA13624 for current-outgoing; Thu, 20 Jun 1996 06:55:18 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA13619 for ; Thu, 20 Jun 1996 06:55:15 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id HAA09538; Thu, 20 Jun 1996 07:55:08 -0600 Date: Thu, 20 Jun 1996 07:55:08 -0600 From: Nate Williams Message-Id: <199606201355.HAA09538@rocky.sri.MT.net> To: Chuck Robey Cc: Andreas Klemm , FreeBSD current Subject: Re: When gcc-2.7.2 hits ctm In-Reply-To: References: Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ Big CTM patches ] > Andreas, I can see why you don't understand yet. Most of the users of > ctm are doing so because they don't have direct connections to the net. I have a hard time believing that 'most' of the users dont' have direct connections. Some do, some have slow connections to the net. And some with slow connections still don't use CTM. :) > usage. I can give a Gig of space, but my University account has a 7.5 MB > limit on it. I think that some folks will have higher limits, some > lower, but the key point is that the amount of space is not under their > control. No amount of planning is going to allow for a 25 megabyte mail > dump. > > That's why I suggested specifically killing the mailing of the gcc, and > allowing folks to separately ftp the ctm update of that one. What would you have the developers do. 1) Fix bugs, add code, make things better 2) Do administration work, and let the remote developers worry about such issues (since they are capable of making sure this doesn't happen). You *are* a remote developer if you're getting the CTM stuff. And, if you can't handle the mail load of the gcc integration, un-subscribe from CTM until it all blows over, ftp everything by hand, and when everything is back to normal re-subscribe. Everything is in your hands and Poul didn't have to do anything, and those users who *can* handle the larger email aren't punished either. Viola, problem solved. Nate