lkml.org 
[lkml]   [2013]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 5/7] Docs: Expectations for bug reporters and maintainers
On Wed, Apr 17, 2013 at 11:23:28AM -0700, Sarah Sharp wrote:
> On Tue, Apr 16, 2013 at 09:15:06PM -0500, Rob Landley wrote:

> > Patches go from the developer, to the maintainer, to one of Linus's
> > lieutenants, to Linus himself. If you submit a patch to a maintainer
> > they owe you a response. The lieutenant (subsystem maintainer) owes
> > that maintainer a response, and Linus (the project's architect) owes
> > the lieutenant a response.

> Do we want to go into this much detail in a document meant for
> frustrated bug reporters? Or perhaps we should create a separate
> document about the kernel maintainer hierarchy and reference it here?

The rule of thumb I tend to give people here is to make sure that the
people who tend to sign off changes to the driver are on the mail. Not
everyone is comfortable with git but if they are that's fairly easy to
do.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2013-05-01 17:41    [W:0.519 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site