Date: Thu, 27 Aug 1998 11:01:58 -0500 From: Chris Csanady <ccsanady@friley-185-114.res.iastate.edu> To: Stefan Eggers <seggers@semyam.dinoco.de> Cc: Jonathan Lemon <jlemon@americantv.com>, freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages Message-ID: <199808271601.LAA05116@friley-185-114.res.iastate.edu> In-Reply-To: Your message of "Thu, 27 Aug 1998 10:41:57 %2B0200." <199808270841.KAA02095@semyam.dinoco.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>> In any case, you can get the same functionality by subscribing >> to cvs-all, and using a procmail filter to weed out what you >> aren't interested in. > >It's not the same. That would increase transfer times significantly >for me as I would have to transfer all log messages instead of just >the kernel related ones. It simply costs money I prefer to spend on >more useful things instead. > >I am just interested in the kernel to get noticed when anything impor- >tant happens there. I don't care much about bugs in user land prog- >rams as they don't lead to the whole machine crashing. > >To me cvs-all, cvs-bin, cvs-ports and cvs-sys sounds like a reasonable >way to split it. The hundreds of lists that previously existed are a >bit too much IMHO. I completely agree with this. I would not mind having fewer lists, but cvs-all has quite a low signal to noise ratio for some of us. I really don't care to see the ports/web/doc commits. Perhaps at least the src commits can be seperated? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808271601.LAA05116>