public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: "Michael D. Crawford" <crawford@goingware.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: Fri, 05 Jan 2001 00:29:05 -0800	[thread overview]
Message-ID: <3A5585D1.5090903@megapathdsl.net> (raw)
In-Reply-To: <3A55447D.995FB159@goingware.com>

Michael D. Crawford wrote:

<snip>


> You might think this is great because of all the extra testing the new users
> will do but I assert that it isn't.  The environment for Linux is quite
> different these days than when 2.2 or 2.0 were released.
> 
> A lot of the people who will be using it are not technically savvy people, and
> many of those who do know technology depend on its reliability for the
> profitability of large businesses but may not read Linus' message that indicates
> this is really just for testing.

Alan's comments were addressed to driver developers, not users.
It's driver developers who need to work with Alan to make sure
he doesn't have to now do twice as much work as he used to
(BTW:  I think this is a mental and physical impossibility).

The distros will ship 2.4.0 kernels whenever they want to, which
will probably be when they think there are no major gotchas in it.

If I remember correctly, when 2.2.0 was released, a similar process
took place.  Alan helped get patches into the 2.0 kernel tree for
a while.  When the 2.3.0 tree was opened up, Linus' attention
shifted completely to that new development tree.  That left Alan
to take up the slack by becoming the maintainer of the 2.2 tree.
Very shortly after Alan moved onto the 2.2 tree, he announced that
the vast amount of his work would be focussed there and not on the
2.0 tree.

As far as I know, 2.0 to 2.2 transition went really quite smoothly,
so this process must be working.

I would suggest that if you are writing drivers for the 2.2 tree,
that you just work with Alan and make sure your code is also in
the 2.4 tree.  Alan's doing you a favor by clearly spelling out
what he can reasonably be expected to accomplish.  If he over-
estimated his ability to process code changes, we'd all be in
a world of hurt and disappointment.

As for users, their fate is in the hands of the distribution
developers.  It's the distribution developers' responsibility
to ship good, solid code.  If you are scared that they won't
do a good job of that, I guess you'll want to wait for one
of their later releases.

Best wishes,

	Miles

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-05  8:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  3:50 Change of policy for future 2.2 driver submissions Michael D. Crawford
2001-01-05  8:29 ` Miles Lane [this message]
2001-01-05 17:31 ` Linus Torvalds
2001-01-09 14:49   ` Hubert Mantel
2001-01-09 14:54     ` Alan Cox
2001-01-09 23:49       ` Jakob Østergaard
2001-01-10  0:02         ` Linus Torvalds
2001-01-10  0:33     ` Ingo Molnar
2001-01-10  1:03       ` Andrea Arcangeli
2001-01-10  1:17         ` Ingo Molnar
2001-01-10  1:40           ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:36 Wayne.Brown
2001-01-08  4:52 Wayne.Brown
2001-01-08 11:07 ` David Weinehall
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway
2001-01-05 17:32 Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts
2001-01-05 17:11 Wayne.Brown
2001-01-05 17:15 ` Alan Cox
2001-01-05 17:23   ` Christoph.Hellwig.
     [not found]     ` <hchÀcaldera.de>
2001-01-05 17:31       ` Alan Cox
2001-01-05  2:41 Alan Cox
2001-01-05  3:27 ` Nicholas Knight
2001-01-05  4:23   ` Mark Hahn
2001-01-05 12:52     ` Daniel Phillips
2001-01-05  6:38   ` Tim Riker
2001-01-05  6:57   ` Andre Tomt
2001-01-05  7:30     ` Gerhard Mack
2001-01-05 11:46   ` Rik van Riel

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=3A5585D1.5090903@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=crawford@goingware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox