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]
Message-ID: <Pine.LNX.4.64.0704230640540.25153@server.thyself>
Date:	Mon, 23 Apr 2007 06:42:24 +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:
>
>>  If there was 1) a maintainer and 2) code that didn't break "coding
>>  standards", would it be included in the kernel?
>
> While I cannot speak for Linus and Andrew, code that fulfills
> these criteria (and is useful to have - reiser4 seems to have
> enough user interest) usually gets accepted.
>
> http://kernelnewbies.org/UpstreamMerge has some hints.

So in conclusion / to answer Eric's question,
1) reiser4 needs a maintainer
2) reiser4 needs the code quality cleaned up
3) Until those two things happen, it's extremely unlikely that it will be 
included in the kernel.

Correct?
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ