From: Chuck Ebbert <76306.1226@compuserve.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dave Jones <davej@redhat.com>,
William Lee Irwin III <wli@holomorphy.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rddunlap@osdl.org>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Subject: Re: Let's make a small change to the process
Date: Wed, 27 Oct 2004 15:50:29 -0400 [thread overview]
Message-ID: <200410271553_MC3-1-8D4F-38E8@compuserve.com> (raw)
On Wed, 27 Oct 2004 at 16:05 +0100 Alan Cos wrote:
> Each 2.6.10rc change I merged is on the basis of reward >> risk.
I'm inclined to even accept very small patches that aren't really
bugfixes, like initmem poisoning and the signal delivery patch
that removes unconditional writes to dr7.
But some of the larger ones scare me, especially when they need
modification to apply cleanly. Even if the mods are clear, there
can be new logic elsewhere that breaks a backported patch.
--Chuck Ebbert 27-Oct-04 15:49:15
next reply other threads:[~2004-10-27 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 19:50 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 2:17 Let's make a small change to the process Chuck Ebbert
2004-10-27 15:05 ` Alan Cox
2004-10-27 20:38 ` Bill Davidsen
2004-10-26 10:44 My thoughts on the "new development model" Ed Tomlinson
2004-10-26 11:09 ` Massimo Cetra
2004-10-26 12:08 ` Paolo Ciarrocchi
2004-10-26 19:03 ` Mathieu Segaud
2004-10-26 20:16 ` Let's make a small change to the process Paolo Ciarrocchi
2004-10-26 20:22 ` William Lee Irwin III
2004-10-26 20:26 ` Paolo Ciarrocchi
2004-10-26 20:33 ` William Lee Irwin III
2004-10-26 20:36 ` Dave Jones
2004-10-26 20:44 ` Paolo Ciarrocchi
2004-10-27 0:51 ` Jan Knutar
2004-10-26 20:48 ` John Richard Moser
2004-10-26 21:00 ` Paolo Ciarrocchi
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=200410271553_MC3-1-8D4F-38E8@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=rddunlap@osdl.org \
--cc=wli@holomorphy.com \
/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.