mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Tilman Schmidt" <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org,
	"Jan Engelhardt" <jengelh@linux01.gwdg.de>,
	"Matthias Andree" <matthias.andree@gmx.de>,
	"Grzegorz Kulewski" <kangur@polcom.net>,
	"Diego Calleja" <diegocg@gmail.com>,
	arjan@infradead.org, caleb@calebgray.com
Subject: Re: Reiser4 Inclusion
Date: Wed, 19 Jul 2006 14:03:54 +0300	[thread overview]
Message-ID: <84144f020607190403y1a659c99oc795ae244390c2ee@mail.gmail.com> (raw)
In-Reply-To: <fake-message-id-1@fake-server.fake-domain>

On 7/19/06, Tilman Schmidt <tilman@imap.cc> wrote:
> You can't have it both ways. Either you want everything in the main
> kernel tree or you don't. Of course there will always be a limbo of
> code waiting for inclusion. But if it has to linger there for too
> long (again: no matter for what reason) then it invalidates the
> whole concept of not having a stable API. And that would be a pity.

You seem to have this idea of everyone having some sacred right of
having their code either in the kernel or supported by the kernel
developers. That's fine, but last I checked, does not apply to Linux.
It is up to the maintainers to decide what's included and what's not.
We obviously don't want _everything_ in the kernel anyway and don't
want to stagnate the kernel development because of out-of-tree code
either. If you're unhappy about maintainer decisions, feel free to
complain to them or better yet, step up to do the necessary legwork to
get the code included. After all, that's how Linux development works.

  parent reply	other threads:[~2006-07-19 11:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  3:02 Caleb Gray
2006-07-17  9:25 ` Arjan van de Ven
2006-07-17 11:48   ` Grzegorz Kulewski
2006-07-17 11:57     ` Alexander Gran
2006-07-17 14:06     ` Diego Calleja
2006-07-17 14:31       ` Grzegorz Kulewski
2006-07-17 15:51         ` Matthias Andree
2006-07-18  7:59           ` Jan Engelhardt
2006-07-18 20:47             ` Matthias Andree
2006-07-19  1:19               ` Joshua Hudson
2006-07-19  9:27               ` Tilman Schmidt
2006-07-19 11:00                 ` Krzysztof Halasa
2006-07-19 11:03                 ` Pekka Enberg [this message]
2006-07-19 15:32                   ` Tilman Schmidt
2006-07-19 19:04                     ` Valdis.Kletnieks
2006-07-19 19:12                       ` Tilman Schmidt
2006-07-19 20:09                         ` Valdis.Kletnieks
2006-07-19 22:36                           ` Tilman Schmidt
2006-07-19 20:29                       ` Jeff V. Merkey
2006-07-19 22:01                         ` Matthias Andree
2006-07-19 22:34                     ` Helge Hafting
2006-07-17 15:52         ` gmu 2k6
2006-07-17 15:57           ` Alexander Gran
2006-07-17 19:01         ` Horst von Brand
2006-07-17 15:13     ` Jeff Anderson-Lee
2006-07-17 15:56       ` Matthias Andree
2006-07-17 20:48       ` Erik Mouw
2006-07-18  0:49         ` Jeff Dike
2006-07-18 11:43           ` Christoph Hellwig
2006-07-17  9:44 ` Patrick McFarland
2006-07-17 11:07 ` Diego Calleja
2006-07-17 14:38 ` Alex Riesen
2006-07-17 18:05 ` Valdis.Kletnieks
2006-07-18 23:10   ` Nix
2006-07-19  6:56 ` Reiser4 ACLs Marc Perkel
2006-07-19 15:03   ` Jan Engelhardt
2006-07-17 22:34 Reiser4 Inclusion linux
     [not found] <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>
2006-07-30 22:02 ` Tilman Schmidt

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=84144f020607190403y1a659c99oc795ae244390c2ee@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=arjan@infradead.org \
    --cc=caleb@calebgray.com \
    --cc=diegocg@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kangur@polcom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    --cc=tilman@imap.cc \
    /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

all inboxes | Powered by JetHome®