linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please release a stable kernel Linux 3.0
Date: Thu, 28 Jun 2007 01:32:23 +0300	[thread overview]
Message-ID: <200706280132.23739.a1426z@gawab.com> (raw)
In-Reply-To: <20070627171149.GZ21478@ftp.linux.org.uk>

Al Viro wrote:
> On Wed, Jun 27, 2007 at 04:53:58PM +0300, Al Boldi wrote:
> > Al Viro wrote:
> > > On Wed, Jun 27, 2007 at 11:18:36AM +0200, Zolt?n HUBERT wrote:
> > > > And as I understand it, this is (was ?) the whole point of
> > > > stable/development kernels. "We" can trust a newer stable
> > > > kernel to be a drop-in replacement for an older stable
> > > > kernel (from the same series), while development kernels
> > > > need time to stabilise with the new whizz-bang-pfouit stuff
> > > > that you all so nicely add.
> > >
> > > "Drop-in" in which sense?  That out-of-tree modules keep working?
> > > Not really...
> >
> > Al, be reasonable.  There are many out-of-tree GPL modules that won't be
> > accepted into mainline, never mind those that shouldn't be accepted. 
> > But these modules do have a right to not be obsoleted by constant API
> > changes.
>
> Modules do not have any rights; it's software...

Ok, this should have been read as kernel/module dev/user right to leverage 
each others code under GPL and out of good-will to yield an increased 
harvest.

> > You are effectively inhibiting the development of an out-of-tree GPL
> > module pool, by constantly pulling the rug under that community.
>
> The same thing happens with any yet-to-be-merged code.
>
> > Do you think this is fair?
>
> Yes, it is fair.  Decision to maintain your code out of tree indefinitely
> is your decision.

It's not my decision, it's the kernel maintainers decision to reject 
inclusion for one reason or another.  One reason could be a simple "we don't 
think this is useful".

Also, I think it's unrealistic to expect thousands of little-used modules to 
be included into mainline.

But, should we hinder that community to grow?


Thanks!

--
Al


  reply	other threads:[~2007-06-27 22:31 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 13:53 Please release a stable kernel Linux 3.0 Al Boldi
2007-06-27 15:52 ` Adrian Bunk
2007-06-27 16:08   ` Chuck Ebbert
2007-06-27 16:26     ` Dmitry Torokhov
2007-06-27 16:26     ` Adrian Bunk
2007-06-27 22:32   ` Al Boldi
2007-06-27 17:11 ` Al Viro
2007-06-27 22:32   ` Al Boldi [this message]
2007-06-27 23:12     ` Al Viro
2007-06-28 15:37       ` Al Boldi
     [not found] <8AH0j-3Qc-11@gated-at.bofh.it>
     [not found] ` <8AH0j-3Qc-9@gated-at.bofh.it>
     [not found]   ` <8B0vZ-r6-5@gated-at.bofh.it>
     [not found]     ` <8B46G-69z-15@gated-at.bofh.it>
     [not found]       ` <8B52G-7C9-5@gated-at.bofh.it>
     [not found]         ` <8BalK-7Ic-39@gated-at.bofh.it>
     [not found]           ` <8BaYr-8tJ-17@gated-at.bofh.it>
2007-06-29 21:05             ` Bodo Eggert
2007-06-29 21:27               ` Rene Herman
2007-06-30  2:11                 ` Daniel Hazelton
2007-06-30 10:50                   ` Rene Herman
     [not found] <fa.ZV8hYZHQHqzfx1dgOFeEVFRogSg@ifi.uio.no>
2007-06-27 14:15 ` Bill Waddington
2007-06-28 11:15   ` Helge Hafting
2007-06-28 15:28     ` William D Waddington
2007-06-28 16:30       ` Alan Cox
2007-06-28 16:39         ` William D Waddington
2007-06-29  0:00           ` Alan Cox
2007-06-28 21:39         ` Al Viro
2007-06-28 22:00         ` Rene Herman
2007-06-28 22:48           ` Alan Cox
2007-06-28 22:45             ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:49 Zoltán HUBERT
2007-06-21 21:54 ` Chuck Ebbert
2007-06-21 22:08 ` Alan Cox
2007-06-21 22:21   ` Zoltán HUBERT
2007-06-22 20:54     ` Willy Tarreau
2007-06-21 22:29 ` Jesper Juhl
2007-06-21 22:34   ` Chuck Ebbert
2007-06-21 23:01     ` Lennart Sorensen
2007-06-21 23:08       ` Chuck Ebbert
2007-06-21 23:36         ` Måns Rullgård
2007-06-21 23:45         ` Arjan van de Ven
2007-06-28 21:15           ` Pavel Machek
2007-06-29 13:41             ` Rafael J. Wysocki
2007-06-29 22:33               ` Pavel Machek
2007-06-22 15:00     ` Rafael J. Wysocki
2007-06-22 17:11       ` Chuck Ebbert
2007-06-22 22:10         ` Rafael J. Wysocki
2007-06-24 20:54         ` Rafael J. Wysocki
2007-06-25 16:38           ` Chuck Ebbert
2007-06-25 23:20             ` Rafael J. Wysocki
2007-06-25 23:23               ` Chuck Ebbert
2007-06-21 22:57   ` Zoltán HUBERT
2007-06-21 23:07     ` Jesper Juhl
2007-06-21 23:23     ` Lennart Sorensen
2007-06-22  8:34     ` Bernd Petrovitsch
2007-06-26 11:59     ` Helge Hafting
2007-06-26 14:37       ` Zoltán HUBERT
2007-06-26 15:04         ` Renato S. Yamane
2007-06-26 19:03         ` Roland Kuhn
2007-06-27  9:18           ` Zoltán HUBERT
2007-06-27  9:54             ` Alan McKinnon
2007-06-27  9:55             ` Al Viro
2007-06-27 14:44             ` Helge Hafting
2007-06-27 16:13             ` Chuck Ebbert
2007-06-29 16:37             ` Gerhard Mack
2007-06-21 23:30   ` Jan Engelhardt
2007-06-21 23:32     ` david
2007-06-22  8:41       ` Jan Engelhardt
2007-06-21 22:52 ` Stefan Richter
2007-06-21 22:59   ` Zoltán HUBERT
2007-06-21 22:58 ` Rene Herman
2007-06-22  3:51 ` Rik van Riel
2007-06-22  9:19 ` Xavier Bestel
2007-06-22  9:45   ` Bernd Petrovitsch
2007-06-23  7:25 ` Chris Snook

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=200706280132.23739.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).