From owner-freebsd-current Wed Jun 19 14:04:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA22518 for current-outgoing; Wed, 19 Jun 1996 14:04:09 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA22469 for ; Wed, 19 Jun 1996 14:03:58 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id WAA22788; Wed, 19 Jun 1996 22:45:31 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id WAA00703; Wed, 19 Jun 1996 22:53:36 +0200 (MET DST) Date: Wed, 19 Jun 1996 22:53:36 +0200 (MET DST) From: Andreas Klemm To: Chuck Robey cc: FreeBSD current Subject: Re: When gcc-2.7.2 hits ctm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Jun 1996, Chuck Robey wrote: > Twice recently I have had ctm mailbomb me with big updates, and I guess > everyone else who uses ctm has had that happen too. Yes, I think we share the same lists, eh ?! ;-) > My mail capacity was > big engough to manage, but I'm just a little worried about the near > future. why... > If some care isn't taken, when the new gcc gets imported into > current, well, gcc is big enough to overflow probably everyone's mailbox, > no matter what size each individual ctm update is limited to. I don't think so. People, who really like to get the source repository are certainly so clever, to have sufficient space ... And, getting current means to get all the nice cool new stuff, you want it, you get it ... > I just hope that ctm is taken into account, when gcc is brought up to > 2.7.2, else there's gonna me one enormous mail snafu. hmmm, ok ... so people be warned ! ;-) > There's several > different ways to handle this, I don't care how it's finally decided, I > just don't want ctm trying to send me 25 megabytes of mail all in one day. Excuse me, I don't know exactly what you mean ... Ok, the worst thing might be, you get all at one, so you fear, your spool space might overflow ... So you mean, the commitments should be done in peaces ?!?! Is that doable ?! When a developer extracts his work on the main src server, what should he do .... cvs committ .... what else ?! The 'beast' works recursive .... Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<<