linux-kernel - What's the staging review and acceptance process?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1271881967.1730.482.camel@Joe-Laptop.home>
Date:	Wed, 21 Apr 2010 13:32:47 -0700
From:	Joe Perches <joe@...ches.com>
To:	Greg KH <gregkh@...e.de>
Cc:	devel@...verdev.osuosl.org, LKML <linux-kernel@...r.kernel.org>
Subject: What's the staging review and acceptance process?

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/