From: Adrian Bunk <bunk@stusta.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Willy Tarreau <w@1wt.eu>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.30-pre1
Date: Mon, 25 Sep 2006 03:23:22 +0200 [thread overview]
Message-ID: <20060925012322.GE4547@stusta.de> (raw)
In-Reply-To: <20060924101753.GB4813@ucw.cz>
On Sun, Sep 24, 2006 at 10:17:53AM +0000, Pavel Machek wrote:
> Hi!
>
> > > Adrian, when you have a doubt whether such a fix should go into next
> > > release, simply tell people about the problem and ask them to test
> > > current driver. If nobody encounters the problem, you can safely keep
> > > the patch in your fridge until someone complains. By that time, the
> > > risks associated with this patch will be better known.
> >
> > It's not that I wanted to upgrade ACPI to the latest version.
> >
> > And my rules are:
> > - patch must be in Linus' tree
> > - I'm asking the patch authors and maintainers of the affected subsystem
> > whether the patch is OK for 2.6.16
>
> I thought stable rules were longer than this... including 'patch must
> be < 100 lines' and 'must be bugfix for serious bug'. Changing rules
> for -stable series in the middle of it seems like a bad idea...
I stated what I'd do with 2.6.16 before I took over maintainance.
> Maybe you can keep -ab with relaxed rules and -stable with original
> rules?
Much would be possible under the assumption I had unlimited time...
> Pavel
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-09-25 1:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 22:23 Linux 2.6.16.30-pre1 Adrian Bunk
2006-09-22 22:38 ` Greg KH
2006-09-22 22:47 ` Adrian Bunk
2006-09-22 23:09 ` Greg KH
2006-09-23 4:56 ` Willy Tarreau
2006-09-23 23:21 ` Adrian Bunk
2006-09-23 23:53 ` Willy Tarreau
2006-09-24 7:46 ` Sergey Vlasov
2006-09-24 18:16 ` Adrian Bunk
2006-09-24 19:46 ` Stefan Richter
2006-09-24 19:44 ` Willy Tarreau
2006-09-24 20:02 ` Willy Tarreau
2006-09-25 1:01 ` Adrian Bunk
2006-09-24 10:17 ` Pavel Machek
2006-09-25 1:23 ` Adrian Bunk [this message]
2006-09-25 8:15 ` Pavel Machek
2006-09-27 5:14 ` Greg KH
2006-09-23 20:49 ` Jean Delvare
2006-09-23 20:57 ` Lee Revell
2006-09-23 21:20 ` Jean Delvare
2006-09-23 22:47 ` Adrian Bunk
2006-09-23 22:33 ` Adrian Bunk
2006-09-23 22:47 ` Lee Revell
2006-09-23 22:58 ` Adrian Bunk
2006-09-23 22:12 ` Adrian Bunk
2006-09-24 10:12 ` Pavel Machek
2006-09-25 1:20 ` Adrian Bunk
2006-09-24 20:25 ` Grant Coady
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=20060925012322.GE4547@stusta.de \
--to=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=w@1wt.eu \
/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.