From: Greg KH <gregkh@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: What's the staging review and acceptance process?
Date: Thu, 22 Apr 2010 13:18:19 -0700 [thread overview]
Message-ID: <20100422201819.GC26924@suse.de> (raw)
In-Reply-To: <20100422101708.69c90142@lxorguk.ukuu.org.uk>
On Thu, Apr 22, 2010 at 10:17:08AM +0100, Alan Cox wrote:
> On Wed, 21 Apr 2010 22:49:02 -0700
> Greg KH <gregkh@suse.de> 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.
> >
> > While a series of unfortunate events did happen to cause this, do you
> > have any evidence of this causing people to go away?
>
> Subjectively the answer is yes I think. More quantatively it was the case.
> I did some measurements long ago with 2.4-ac and there was direct and
> clear connection between two things and patch submission/activity levels.
> One was 'cycle time' (ie time from submit->response->tree) - the other was
> putting the name of the contributor in the per -ac patch summaries that
> used to get mailed out.
Yeah, I know I liked seeing my name there, that was very nice to have :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-04-22 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 20:32 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
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 [this message]
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=20100422201819.GC26924@suse.de \
--to=gregkh@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome