Tweaking the patch submission process

[Matt Mackall]

On Tue, 2008-10-28 at 11:10 -0500, Matt Mackall wrote:
> We're trying to smooth out some of the bumps in our workflow here and
> one of the things we've come up with is to assign specific people to
> handle various areas of the code.
> 
> Initially, we're going to try something like this:
> 
> Patrick: Windows support, convert extension, mq
> Dirkjan: hgweb, named branches
> Matt: revlog, merge, other core pieces
> Benoit: trivial patches and patch triage
> 
> So when you send a patch, please add a cc: for the appropriate person
> from the above list. That way we can avoid multiple people queueing the
> same patch, or worse, having nobody queue it. If you guess wrong, we'll
> try to sort it out.
> 
> These areas are also here, we'll try to document them more clearly as we
> get more experience with this:
> 
> http://www.selenic.com/mercurial/wiki/index.cgi/CrewRepository

Alright, it looks like Mailman is brain-damaged when it comes to cc:
handling and is helpfully stripping off any cc: to someone it thinks is
a list member. Please instead send patches TO someone listed above and
CC the list.

For the curious, here's what's happening: Mailman has a nice feature to
avoid sending duplicate messages to anyone who has nodupe set in mail
preferences, which happens to be the default. This is implemented by
removing their address from the recipient list in the SMTP
'envelope' (and not connected with the headers inside the message). If
they stopped here, everything would be fine. But in addition to that,
they also remove those names from the cc: list (but not to:, etc.) so
that cc: lists don't grow inordinately. And naturally, there's no option
to disable it.

-- 
Mathematics is the supreme nostalgia of our time.