From: Greg KH <gregkh@suse.de>
To: Joe Perches <joe@perches.com>
Cc: devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: What's the staging review and acceptance process?
Date: Wed, 21 Apr 2010 23:12:42 -0700 [thread overview]
Message-ID: <20100422061242.GA28539@suse.de> (raw)
In-Reply-To: <1271915718.1730.687.camel@Joe-Laptop.home>
On Wed, Apr 21, 2010 at 10:55:18PM -0700, Joe Perches wrote:
> On Wed, 2010-04-21 at 22:49 -0700, Greg KH wrote:
> > On Wed, Apr 21, 2010 at 09:25:57PM -0700, Joe Perches wrote:
> > > On Wed, 2010-04-21 at 20:45 -0700, Greg KH wrote:
> > > > That caused the huge backlog staring at me right now.
> > > Which likely discouraged the new contributors who
> > > submitted stuff still in that backlog.
> > do you have any evidence of this causing people to go away?
>
> I think it's pretty established that response delays
> cause losses of one type or another.
Established where?
What type of losses?
> > > Unfortunately, your process has been opaque until you
> > > personally handle it.
> > Yes, like all subsystem maintainers, right?
>
> Not really, patchwork shows status immediately.
Immediately when someone does something with it, right? So, the same as
my development cycle?
> > Are you volunteering?
>
> Guess so.
For now, let me get through this patch queue. If you could review
anything new coming in, that would be greatly appreciated, especially to
weed out the problem patches. After everything is caught up, we can
revisit it, ok?
thanks,
greg k-h
next prev parent reply other threads:[~2010-04-22 6:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 20:32 What's the staging review and acceptance process? Joe Perches
2010-04-22 3:45 ` Greg KH
2010-04-22 4:25 ` Joe Perches
2010-04-22 5:49 ` Greg KH
2010-04-22 5:55 ` Joe Perches
2010-04-22 6:12 ` Greg KH [this message]
2010-04-22 6:28 ` Joe Perches
2010-04-22 6:35 ` Jaya Kumar
2010-04-22 6:42 ` Olivier Galibert
2010-04-22 19:58 ` John W. Linville
2010-04-22 20:06 ` Randy Dunlap
2010-04-22 20:17 ` Greg KH
2010-04-22 9:25 ` Stefan Richter
2010-04-22 9:17 ` Alan Cox
2010-04-22 20:18 ` Greg KH
2010-04-22 22:46 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100422061242.GA28539@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.