Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-17 Thread Mikhail Sobolev
1. Do nothing, everything's fine just the way it is -1 2. Do a + b +1 3. Do a + b + c 0 And, separately, to use summaries instead of full messages for bugs/patches/etc. +1 -- Misha msg05721/pgp0.pgp Description: PGP signature ___

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-16 Thread Bryan Fullerton
On Thursday, January 16, 2003, at 12:12 AM, Barry A. Warsaw wrote: 3. Do a + b + c I don't entirely understand this -1/0/+1 thing, but option 3 would be my preference. Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED]

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-16 Thread Barry A. Warsaw
BF == Bryan Fullerton [EMAIL PROTECTED] writes: BF I don't entirely understand this -1/0/+1 thing, but option 3 BF would be my preference. http://www.python.org/peps/pep-0010.html -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED]

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-16 Thread Marilyn Davis
1. Do nothing, everything's fine just the way it is +0 2. Do a + b +1 3. Do a + b + c +1 Gee, eVote could help here. I'm dawdling with the install process and documentation, but soon. On an eVoted list, for this poll, you'd send a message to the list address that says: eVote poll

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-16 Thread Terri Oda
1. Do nothing, everything's fine just the way it is 0 2. Do a + b +1 3. Do a + b + c 0 4. do a + b + post summaries to mailman-developers +1 I don't mind getting the SF messages, even on those my poor laptop's on dialup days, but to be honest, they get procmailed to another folder and I tend

[Mailman-Developers] Sourceforge notifications considered harmful

2003-01-15 Thread Tom Neff
It completely sucks, and has completely sucked ever since the decision was made a few months ago, that Mailman-Developers gets Cc'd on every Sourceforge update. I'm sure Barry (or whoever) felt they were doing a service, but it has practically killed discussion here and cost us many, many

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-15 Thread Matthew Davis
* Tom Neff ([EMAIL PROTECTED]) wrote: If you don't actually want to have a Developers discussion list, then shut it down and let people submit stuff via Sourceforge only. If you do want one, let us have one. How about a mailman-developers and mailman-bugsandpatches list?

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-15 Thread Barry A. Warsaw
TN == Tom Neff [EMAIL PROTECTED] writes: TN It completely sucks, and has completely sucked ever since the TN decision was made a few months ago, that Mailman-Developers TN gets Cc'd on every Sourceforge update. I'm sure Barry (or TN whoever) felt they were doing a service, but

Re: [Mailman-Developers] Sourceforge notifications considered harmful

2003-01-15 Thread Jon Parise
On Thu, Jan 16, 2003 at 12:12:07AM -0500, Barry A. Warsaw wrote: a. I create a [EMAIL PROTECTED] list b. Send SF tracker messages to this list instead of mailman-developers c. Possibly (and I think optimally), retire mailman-checkins and send the cvs diffs to mailman-coders as well.