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]
Date:	Thu, 27 Aug 2009 11:22:19 -0700
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	stable-review@...nel.org
Cc:	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Would it help to encourage users to read/test stable-review patches

Just thinking out loud here.

We get development review eyes on stable patches during submission
into a subsystem, and perhaps 1-2 user tests then. Typically patches
are pretty easy to review for stable submission but I'm wondering
about cases where things are not so clear and perhaps we want better
testing and are less willing to take a fix into stable than on latest
rc. Also what if a user just wants to test an entire series queues up
for stable-review, is there a single all-in-one file user can just
patch -p1 to help test prior to getting the next stable release made?
Do we want more user exposure to stable-review mailing list or is just
a few developer eyes enough?

  Luis
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ