linux-um archives
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: anton.ivanov@cambridgegreys.com
Cc: richard@nod.at, linux-um@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: add a new User Mode Linux HowTo
Date: Wed, 9 Sep 2020 11:55:32 -0600	[thread overview]
Message-ID: <20200909115532.42a96ddc@lwn.net> (raw)
In-Reply-To: <20200907092124.17599-1-anton.ivanov@cambridgegreys.com>

On Mon,  7 Sep 2020 10:21:24 +0100
anton.ivanov@cambridgegreys.com wrote:

Sorry, I'd missed the fact that there's a v2; my comments from v1 still
apply, though, it seems.

> diff --git a/Documentation/virt/uml/user_mode_linux.rst b/Documentation/virt/uml/user_mode_linux-2.4.rst
> similarity index 99%
> rename from Documentation/virt/uml/user_mode_linux.rst
> rename to Documentation/virt/uml/user_mode_linux-2.4.rst
> index de0f0b2c9d5b..ed5a698cd710 100644
> --- a/Documentation/virt/uml/user_mode_linux.rst
> +++ b/Documentation/virt/uml/user_mode_linux-2.4.rst
> @@ -10,6 +10,10 @@ User Mode Linux HOWTO
>  This document describes the use and abuse of Jeff Dike's User Mode
>  Linux: a port of the Linux kernel as a normal Intel Linux process.
>  
> +*Note: - this howto is historic and correct as of kernel versions
> +~ 2.4. For more up-to-date information please refer to the newer
> +user_mode_linux_howto_v2.*

So why are we keeping this version around?  The 5.x kernel doesn't need to
document what was happening in 2.4... ?

Thanks,

jon

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2020-09-09 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  9:21 [PATCH v2] docs: add a new User Mode Linux HowTo anton.ivanov
2020-09-09 17:55 ` Jonathan Corbet [this message]
2020-09-09 18:57   ` Anton Ivanov

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=20200909115532.42a96ddc@lwn.net \
    --to=corbet@lwn.net \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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