Patch handling

[Michael Ellerman]

Hi Sean,

Well I think that's been at least in part caused by the fact that Martin's 
spent the last two weeks at conferences. And that some of the patches are for 
fairly trivial UI issues when Martin's still thinking about some of the 
bigger issues.

I imagine jk's already mentioned patchwork 
(http://ozlabs.org/~jk/projects/patchwork/) to Martin. It's a cool little 
script that catches patches from the mailing list and then lets you manage 
them, like so: http://ozlabs.org/ppc64-patches/

cheers

On Tue, 10 May 2005 22:43, Sean Russell wrote:
> 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.

-- 
Michael Ellerman
IBM OzLabs

email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person