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: <200607250757.00643.a1426z@gawab.com>
Date:	Tue, 25 Jul 2006 07:57:00 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org

H. Peter Anvin wrote:
> Al Boldi wrote:
> > Respect what?  The process or the content?
> >
> > Rejecting content due to disrespect for process guidelines would be
> > rather sad.
>
> No, it's not.  That's what you have to do to keep the kernel maintainable.
>
> > If the content is worth its salt, it should be accepted w/o delay, then
> > modified to comply with the process guidelines as necessary.  It's what
> > the GPL allows, afterall.
>
> Uhm, no.  That's basically "throw it over the fence and let someone
> else fix the crap."  Fix it first, then it can go in.

Sure, it would be terrible, if we started to accept "crap", but I wouldn't 
consider content that is worth its "salt", like reiserfs4, to be "crap".

Rejection of content should be based on technical merits only, and no process 
guidelines should stay in the way of its preliminary acceptance.  Otherwise, 
we would be asking for a return to a bureaucratic system that inhibits 
innovation, which I'm sure is not the intention of anybody, I hope.

BTW, this does not mean that impoliteness should be rewarded, on the 
contrary, impoliteness has no place anywhere, and should just be ignored, 
even if the content is worth its salt.

Thanks!

--
Al

-
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