Patch handling

[Sean Russell]

Hey,

One thing I've been noticing is that patches sent to this mailing list seem to 
get lost a lot by Martin.  There's enough traffic that I'm wondering if it 
might be useful (for Martin) to have a separate mailing list exclusively for 
patch submissions?  Or, failing that, extend the ML protocol to say that, if 
you *respond* to a patch submission, then you should *strip* the [PATCH] tag 
out of the subject so that subject filters can be useful.

When you get to a certain level of traffic, there's some justification for 
splitting a mailing list, especially in the case of patch submissions.  And 
I'd say that it might be acceptable to break ML "good practices" to munge the 
"reply-to" field of that list  so that it points back at the discussion list.

Anyway, just a thought.  There are already enough contributions that Martin 
seems to be experiencing the Linus Effect already.

-- 
### SER   
### Deutsch|Esperanto|Francaise|Linux|XML|Ruby|Haskell|Java|Aikido
### http://www.ser1.net       jabber.com:ser  ICQ:83578737 
### GPG: http://www.ser1.net/Security/ser_public.gpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050510/99b87cdd/attachment.pgp