[lkml]   [2002]   [Jan]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: A modest proposal -- We need a patch penguin
On Wednesday 30 January 2002 07:49 am, Matthew D. Pitts wrote:
> Chris,
> Thank you for saying this... I have things I would like do/add to the
> kernel and I am not sure who to send them to.

No, if you're not a maintainer then you still send them to the maintainer in

The interesting question is, who does THAT maintainer send them to. (We seem
to be heading for a four-tiered system, with Linus at the top, a dozen or so
lieutenants under him, and then the specific maintainers under them. With
individual developers submitting patches being the fourth tier. Patches go
from developer, to maintainer, to lieutenant, to linus.)

This doesn't sound like a bad thing for scalability reasons, and should also
help address the "I sent my patch directly to linus a dozen times and I
didn't hear back" problem.

The problem right now is a lot of the maintainers don't seem to know who
their corresponding lieutenant is. We're still waiting for clarification
from Linus...

> Also, is there presently a maintainer for Supermount? If not, I would be
> willing to pick it up for 2.5.x, as it is one of the things I want to work
> on.

I didn't spot one in MAINTAINERS. The email at the top of "mount.h" says:

> * Author: Marco van Wieringen <>

So that might be a good person to ask. Of course who knows how old that
email address is... :)

> Matthew D. Pitts

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:18    [W:0.348 / U:0.512 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site