From: Chris Wright <chrisw@sous-sol.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: stable-review@kernel.org, linux-kernel@vger.kernel.org,
Greg KH <greg@kroah.com>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: Would it help to encourage users to read/test stable-review patches
Date: Thu, 27 Aug 2009 11:29:52 -0700 [thread overview]
Message-ID: <20090827182952.GC10360@sequoia.sous-sol.org> (raw)
In-Reply-To: <43e72e890908271122l6b08aaa5lc66de78301c7c88d@mail.gmail.com>
* Luis R. Rodriguez (mcgrof@gmail.com) wrote:
> 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.
Typically in this case it's either too risky for -stable period, or
we ask for resubmission after it has had more time upstream (through
another -rc cycle, for example).
> 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?
There is a queue that can be applied w/ quilt (or any similar tool that
can handles patches + series file). This is kept here:
http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git
> Do we want more user exposure to stable-review mailing list or is just
> a few developer eyes enough?
More review never hurts, but do you think there's a specific lack or
problem? Thanks for thinking about -stable ;-)
thanks,
-chris
next prev parent reply other threads:[~2009-08-27 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 18:22 Would it help to encourage users to read/test stable-review patches Luis R. Rodriguez
2009-08-27 18:29 ` Chris Wright [this message]
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=20090827182952.GC10360@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.