[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] CVSROOT/loginfo
From:       Rob Kaper <cap () capsi ! com>
Date:       2001-11-05 16:48:05
[Download RAW message or body]

On Mon, Nov 05, 2001 at 04:41:09PM +0100, Thomas Zander wrote:
> Well, you would always have people who just want everything and do
> filtering client side (I don't want to subscribe to another mailing list
> if I want to monitor a module for a week)

There will still be kde-cvs which mails all. The CVS server would just also
mail more fine-grained. Thus, a commit would result in two mails: the
default (as is now) and one for a smaller list.

> So your 'cut down on resources' is just not correct. The machine would
> have to sent the email twice at least.

True, but mail.kde.org would have to send _a lot_ less mail if people could
subscribe to kde-i18n-cvs, koffice-cvs etcetera seperately. We're not
terribly hindered by having different mailinglists for different areas of
development either.

> Again; if you have a procmail on the machine that does the mailing list it
> could very easily do the forwarding for you. This is not something the CVS
> server should decide, this is something the mail server should do, simply
> because of who does what maintainance.

Well, if someone can configure mail.kde.org to send all kdenonbeta/atlantik
mails (with diff) to my mailinglist, I'm happy.

If it needs to be filtered client side, we're sending a lot of data through
the Internet and modems of subscribers which gets filtered to /dev/null
immediately.

> I have this solution implemented in my company on the mailbox, and I am
> sure I am not the only one who can create the procmail entries for this.

Your company doesn't have a 14k4 dial-up, does it? :-)

Rob
-- 
Rob Kaper     | "They that can give up essential liberty to obtain a little
cap@capsi.com | temporary safety deserve neither liberty nor safety."
www.capsi.com | - Benjamin Franklin, Historical Review of Pennsylvania, 1759

[prev in list] [next in list] [prev in thread] [next in thread]