From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: stable-review@kernel.org
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
Chris Wright <chrisw@sous-sol.org>
Subject: Would it help to encourage users to read/test stable-review patches
Date: Thu, 27 Aug 2009 11:22:19 -0700 [thread overview]
Message-ID: <43e72e890908271122l6b08aaa5lc66de78301c7c88d@mail.gmail.com> (raw)
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
next reply other threads:[~2009-08-27 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 18:22 Luis R. Rodriguez [this message]
2009-08-27 18:29 ` Chris Wright
2009-08-27 19:09 ` Luis R. Rodriguez
2009-08-28 8:23 ` Stefan Richter
2009-08-30 17:18 ` Tilman Schmidt
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=43e72e890908271122l6b08aaa5lc66de78301c7c88d@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@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®