From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@suse.de>
Cc: devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: What's the staging review and acceptance process?
Date: Wed, 21 Apr 2010 13:32:47 -0700 [thread overview]
Message-ID: <1271881967.1730.482.camel@Joe-Laptop.home> (raw)
Hi Greg.
Sice your fosdem talk and tuxradar article came out there
have been many patches against staging by new contributors
(I did some too) that seem to get no feedback or get dropped
without comment. Because many of these patches are first
attempts, probably most of them should not be applied in the
first submitted form. I comment on some every once in awhile,
but the number of patches appear to go unnoticed or untracked
seems quite high.
Do you have enough bandwidth to keep these new contributors
engaged? Anything I can do to help?
What is your current review/notify/accept/reject workflow?
Perhaps a patchwork queue for staging might help track these
patches and with more feedback or reviewers, get them in
shape to be applied.
next reply other threads:[~2010-04-21 20:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 20:32 Joe Perches [this message]
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
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=1271881967.1730.482.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®