linux-kernel - Re: Question about Reiser4

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:	Mon, 23 Apr 2007 06:14:04 +0000 (GMT)
From:	William Heimbigner <icxcnika@....tar.cc>
To:	Rik van Riel <riel@...hat.com>
cc:	Eric Hopper <hopper@...ifarious.org>, linux-kernel@...r.kernel.org
Subject: Re: Question about Reiser4

On Mon, 23 Apr 2007, Rik van Riel wrote:
> William Heimbigner wrote:
>
>>  However, is the code really in such a shape that the community doesn't
>>  want to maintain it? Obviously there's a significant number of people
>>  interested in reiser4 - if there weren't, questions like this wouldn't
>>  keep getting asked.
>
> There are people interested in using it, yes.
>
> However, nobody appears to have stepped up to maintain the code.
> If somebody really wanted to maintain the code, there would be a
> new maintainer already.

On that note, what exactly is wanted for (assuming there was a maintainer) 
reiser4 to be suitable for inclusion in the kernel? To my knowledge (and 
I'll admit, I haven't looked in to it very far) the primary reason for 
rejection was that it broke coding standards.

If there was 1) a maintainer and 2) code that didn't break "coding 
standards", would it be included in the kernel?

William Heimbigner
icxcnika@....tar.cc
-
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/