linux-kernel - Re: Reiser4 Inclusion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Jul 2006 14:03:54 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Tilman Schmidt" <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org,
	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>,
	"Matthias Andree" <matthias.andree@....de>,
	"Grzegorz Kulewski" <kangur@...com.net>,
	"Diego Calleja" <diegocg@...il.com>, arjan@...radead.org,
	caleb@...ebgray.com
Subject: Re: Reiser4 Inclusion

On 7/19/06, Tilman Schmidt <tilman@...p.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/