Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751860AbbLLOGM (ORCPT ); Sat, 12 Dec 2015 09:06:12 -0500 Received: from mail-oi0-f53.google.com ([209.85.218.53]:33744 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750862AbbLLOGK (ORCPT ); Sat, 12 Dec 2015 09:06:10 -0500 MIME-Version: 1.0 In-Reply-To: References: <20151212053548.GO20997@ZenIV.linux.org.uk> Date: Sat, 12 Dec 2015 12:06:08 -0200 Message-ID: Subject: Re: README Cleanup Project From: Diego Viola To: Richard Weinberger Cc: Al Viro , LKML , Trivial patch monkey , Jonathan Corbet Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1208 Lines: 36 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 wrote: > On Sat, Dec 12, 2015 at 12:51 PM, Diego Viola 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/