public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Diego Viola <diego.viola@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] README: cosmetic fixes
Date: Thu, 10 Dec 2015 11:34:23 -0700	[thread overview]
Message-ID: <20151210113423.168f8b4d@lwn.net> (raw)
In-Reply-To: <1449345010-12512-1-git-send-email-diego.viola@gmail.com>

I've applied this to the docs tree.  I'd sure rather see an effort to
update this file instead of tweaking it, though.  For example:

> @@ -300,7 +300,7 @@ COMPILING the kernel:
>     kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
>     /boot/bzImage.  To use the new kernel, save a copy of the old image
>     and copy the new image over the old one.  Then, you MUST RERUN LILO
> -   to update the loading map!! If you don't, you won't be able to boot
> +   to update the loading map! If you don't, you won't be able to boot
>     the new kernel image.
>  
>     Reinstalling LILO is usually a matter of running /sbin/lilo. 

I somehow suspect that very few of us actually MUST RERUN LILO in 2015...

Thanks,

jon

  reply	other threads:[~2015-12-10 18:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05 19:50 [PATCH] README: cosmetic fixes Diego Viola
2015-12-10 18:34 ` Jonathan Corbet [this message]
2015-12-11  3:06   ` Diego Viola
2016-01-17 22:54   ` Diego Viola
2016-01-18  9:44     ` Jiri Kosina
2016-01-18 13:41       ` Diego Viola
2016-01-18 19:53       ` Diego Viola
2016-01-18 22:40         ` Jonathan Corbet
2016-01-19  1:32           ` Diego Viola
2016-01-19  2:40             ` Diego Viola
2016-01-19  6:24               ` Diego Viola
2016-01-25 19:40 ` Jonathan Corbet
2016-01-28 18:23   ` Diego Viola

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151210113423.168f8b4d@lwn.net \
    --to=corbet@lwn.net \
    --cc=diego.viola@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox