All of lore.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-rc1-mm1
Date: 10 Feb 2004 01:59:35 GMT	[thread overview]
Message-ID: <c09du7$qnj$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20040209022453.44e7f453.akpm@osdl.org

In article <20040209022453.44e7f453.akpm@osdl.org>,
Andrew Morton  <akpm@osdl.org> wrote:
| Stian Jordet <liste@jordet.nu> wrote:
| >
| > man, 09.02.2004 kl. 10.40 skrev Andrew Morton:
| > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3-rc1/2.6.3-rc1-mm1/
| > 
| > Pretty, pretty please take Karstein Keil's big isdn update from
| > 
| > ftp://ftp.isdn4linux.de/pub/isdn4linux/kernel/v2.6
| > 
| 
| Boggle.  That thing is 1.8MB.
| 
|  163 files changed, 25877 insertions(+), 22424 deletions(-)
| 
| This is the first time that anyone told me that it even existed.  How on
| earth could a patch to a major subsystem grow to such a size in such
| isolation?  When we're at kernel version 2.6.3!

If I read the reply right, Linus neither accepted nor rejected it?

| How mature is this code?  What is its testing status?  What is the size of
| its user base?  Is it available as individual, changelogged patches?
| 
| It would be crazy to simply shut our eyes and slam something of this
| magnitude into the tree.  And it is totally unreasonable to expect
| interested parties to be able to review and understand it.
| 
| Could someone please tell me how this situation came about, and what we can
| do to prevent any reoccurrence?

We've had this discussion before, haven't we? And all the solutions
seemed to involve not having just one person approve things, which isn't
likely to change. I don't recall seeing WHEN it was sent to Linus, but
clearly something working in 2.4 and not in 2.6 probably shouldn't wait
years for 2.8.

I guess the real question is how invasive it is, this isn't the first
time I've heard that 2.6 ISDN doesn't work, so it's not as if putting it
in -mm would break ISDN, the question is how many other things are
touched and might break.

At least it seems to have been widely tested, and is based on something
which is in a stable kernel. A maintainer's lot is not a happy one, and
you have my sympathy.

Maybe leave it in -mm for a bit and not promote it until people have a
chance to really beat on it?
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  parent reply	other threads:[~2004-02-10  2:00 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  9:40 2.6.3-rc1-mm1 Andrew Morton
2004-02-09  9:40 ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09  9:50 ` 2.6.3-rc1-mm1 Stian Jordet
2004-02-09  9:50   ` 2.6.3-rc1-mm1 Stian Jordet
2004-02-09 10:24   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 10:24     ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 10:29     ` 2.6.3-rc1-mm1 Stian Jordet
2004-02-09 10:29       ` 2.6.3-rc1-mm1 Stian Jordet
2004-02-09 11:56     ` 2.6.3-rc1-mm1 Karsten Keil
2004-02-09 11:56       ` 2.6.3-rc1-mm1 Karsten Keil
2004-02-09 19:22       ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 19:22         ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10  2:25         ` 2.6.3-rc1-mm1 Karsten Keil
2004-02-10  2:25           ` 2.6.3-rc1-mm1 Karsten Keil
     [not found]           ` <20040210022343.4ebbc186.akpm@osdl.org>
2004-02-10 17:59             ` 2.6.3-rc1-mm1 Karsten Keil
2004-02-10  1:59     ` bill davidsen [this message]
2004-02-09 14:18 ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-09 14:18   ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-09 23:58   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 23:58     ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10  0:05     ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-10  0:05       ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-11 23:53     ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-11 23:53       ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-09 14:26 ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-09 16:44 ` 2.6.3-rc1-mm1 Dominik Kubla
2004-02-09 16:44   ` 2.6.3-rc1-mm1 Dominik Kubla
2004-02-09 17:42   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 17:42     ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 16:54 ` 2.6.3-rc1-mm1 James Morris
2004-02-09 16:54   ` 2.6.3-rc1-mm1 James Morris
2004-02-09 20:02 ` 2.6.3-rc1-mm1 Karl Vogel
2004-02-10 19:45 ` 2.6.3-rc1-mm1 Brian Jackson
2004-02-10 19:45   ` 2.6.3-rc1-mm1 Brian Jackson
2004-02-10 21:05   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10 21:05     ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10 23:51 ` 2.6.3-rc1-mm1 (SELinux + ext3 + nfsd oops) Chris PeBenito
2004-02-11  2:29   ` James Morris
2004-02-11  2:29     ` James Morris
2004-02-11  3:45     ` Chris PeBenito
2004-02-11  5:03       ` James Morris
2004-02-11  5:03         ` James Morris
2004-02-11 17:08 ` 2.6.3-rc1-mm1 Mark Haverkamp
2004-02-14  2:04 ` VM Acct patch (was Re: 2.6.3-rc1-mm1) Eugene Teo

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='c09du7$qnj$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.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.