| 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
| ||
|
Date: Sat, 12 Dec 2015 12:06:08 -0200 From: Diego Viola <diego.viola@...il.com> To: Richard Weinberger <richard.weinberger@...il.com> Cc: Al Viro <viro@...iv.linux.org.uk>, LKML <linux-kernel@...r.kernel.org>, Trivial patch monkey <trivial@...nel.org>, Jonathan Corbet <corbet@....net> Subject: Re: README Cleanup Project I agree, I would like to apologize for this drama, I never intended to create any flamewars or anything. I also have nothing against LILO itself which I used to use, it used to work great for me. I just love Linux and I want to do what I can (and my best) to try to improve it. Thanks, Diego On Sat, Dec 12, 2015 at 10:43 AM, Richard Weinberger <richard.weinberger@...il.com> wrote: > On Sat, Dec 12, 2015 at 12:51 PM, Diego Viola <diego.viola@...il.com> wrote: >> Why does the Linux kernel keep outdated cruft like this in tree? > > depends on the eye of the beholder. :-) > >> If you need lilo you can just run /sbin/lilo yourself, there is no >> need for this to be in the kernel, especially when the project is >> being phased out already. >> >> Should I send a patch removing all lilo entries from the project? > > You can do a patch which improves the existing README. > Removing stuff you don't like is not an improvement. > > -- > Thanks, > //richard -- 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