From: Jonathan Corbet <corbet@lwn.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: linux-um@lists.infradead.org, linux-doc@vger.kernel.org, richard@nod.at
Subject: Re: [PATCH] docs: add a new User Mode Linux HowTo
Date: Wed, 9 Sep 2020 13:40:21 -0600 [thread overview]
Message-ID: <20200909134021.290ea546@lwn.net> (raw)
In-Reply-To: <14181df1-60a4-530e-e7f2-df4e1a2972a1@cambridgegreys.com>
On Wed, 9 Sep 2020 20:37:35 +0100
Anton Ivanov <anton.ivanov@cambridgegreys.com> wrote:
> >> +Create a sparse raw disk image:
> >> +
> >> +.. code-block:: shell
> >> +
> >> + dd if=/dev/zero of=disk_image_name bs=1 count=1 seek=16G
> >
> > I'd honestly do without all these code-block directives as well; they
> > clutter things considerably for little advantage.
>
> I can merge most of these into a couple of code snippets. I would like
> to leave the content though. As UML does not have an official installer,
> the only way to install it is to build images and there is not that much
> information on this on the net. The only well written piece on the
> subject is > 10 years old and becoming a bit out of date.
Don't misunderstand me - the code is fine and welcome. It's the
".. code-block::" directives that I'm taking issue with. I'd rather see
ordinary literal blocks instead.
Thanks,
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: richard@nod.at, linux-um@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: add a new User Mode Linux HowTo
Date: Wed, 9 Sep 2020 13:40:21 -0600 [thread overview]
Message-ID: <20200909134021.290ea546@lwn.net> (raw)
In-Reply-To: <14181df1-60a4-530e-e7f2-df4e1a2972a1@cambridgegreys.com>
On Wed, 9 Sep 2020 20:37:35 +0100
Anton Ivanov <anton.ivanov@cambridgegreys.com> wrote:
> >> +Create a sparse raw disk image:
> >> +
> >> +.. code-block:: shell
> >> +
> >> + dd if=/dev/zero of=disk_image_name bs=1 count=1 seek=16G
> >
> > I'd honestly do without all these code-block directives as well; they
> > clutter things considerably for little advantage.
>
> I can merge most of these into a couple of code snippets. I would like
> to leave the content though. As UML does not have an official installer,
> the only way to install it is to build images and there is not that much
> information on this on the net. The only well written piece on the
> subject is > 10 years old and becoming a bit out of date.
Don't misunderstand me - the code is fine and welcome. It's the
".. code-block::" directives that I'm taking issue with. I'd rather see
ordinary literal blocks instead.
Thanks,
jon
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2020-09-09 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 14:11 [PATCH] docs: add a new User Mode Linux HowTo anton.ivanov
2020-09-04 14:11 ` anton.ivanov
2020-09-06 7:56 ` Mike Rapoport
2020-09-06 7:56 ` Mike Rapoport
2020-09-06 16:59 ` Anton Ivanov
2020-09-06 16:59 ` Anton Ivanov
2020-09-09 17:52 ` Jonathan Corbet
2020-09-09 17:52 ` Jonathan Corbet
2020-09-09 17:54 ` Randy Dunlap
2020-09-09 17:54 ` Randy Dunlap
2020-09-09 19:37 ` Anton Ivanov
2020-09-09 19:37 ` Anton Ivanov
2020-09-09 19:40 ` Jonathan Corbet [this message]
2020-09-09 19:40 ` Jonathan Corbet
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=20200909134021.290ea546@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.