mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Chris Wright" <chrisw@sous-sol.org>,
	stable-review@kernel.org, linux-kernel@vger.kernel.org,
	"Greg KH" <greg@kroah.com>,
	"Christian Stöveken" <launchpad.net@excogitation.de>
Subject: Re: Would it help to encourage users to read/test stable-review  patches
Date: Fri, 28 Aug 2009 10:23:38 +0200	[thread overview]
Message-ID: <4A97940A.7020703@s5r6.in-berlin.de> (raw)
In-Reply-To: <43e72e890908271209mdbaaf03l820aade2266eb54c@mail.gmail.com>

Luis R. Rodriguez wrote:
>> More review never hurts, but do you think there's a specific lack or
>> problem?
> 
> Not really, I was thinking about the fellow Ubunteros users who tend
> to not have a clue but sometimes enough good will to want to help. If
> the average user understood better the upstream process then perhaps
> it would become clearer to them the importance of stable patches and
> stable-review.

Shouldn't these people rather get started with "the other stable
kernel", called 2.6.x-rcZ?  And the next level would be to either test
-next or follow the master branch of a subsystem development tree of
their interest.

I think it could be more effective overall to activate more people who
watch for regressions in the mainline, send qualified and early
regression reports, and test candidate fixes.  A side effect of better
-rc kernels will be a shallower 2.6.x.y branch queue.

Patches which are submitted for stable-review should already have been
tested as part of the upstream kernel on affected and unaffected
systems.  As Chris wrote, patches which obviously need further field
testing when backported to -stable are per definition too risky for
-stable in the first place.  -stable submission should be low-risk
cherry-picking.

> Bringing users closer to stable-review to me indicates
> more users would understand the stable process and therefore would
> stop bitching to me when a 'non-cirtical' fix never made it into their
> ancient stable. Cc'ing one of those.

Ah, you have especially /these/ people in mind.  Well, set up a clever
procmail filter which autoresponds with a pointer to
Documentation/stable_kernel_rules.txt... :-)
-- 
Stefan Richter
-=====-==--= =--- ===--
http://arcgraph.de/sr/

  reply	other threads:[~2009-08-28  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 18:22 Luis R. Rodriguez
2009-08-27 18:29 ` Chris Wright
2009-08-27 19:09   ` Luis R. Rodriguez
2009-08-28  8:23     ` Stefan Richter [this message]
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=4A97940A.7020703@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=launchpad.net@excogitation.de \
    --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 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®