All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, thuth@redhat.com, berrange@redhat.com,
	armbru@redhat.com, f4bug@amsat.org, marcandre.lureau@gmail.com,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [RFC PATCH] docs/system: add a gentle prompt for the complexity to come
Date: Wed, 3 Mar 2021 13:41:02 -0500	[thread overview]
Message-ID: <eb5cc2cd-111d-84ea-910d-42aedfceef2f@redhat.com> (raw)
In-Reply-To: <20210301112741.31047-1-alex.bennee@linaro.org>

On 3/1/21 6:27 AM, Alex Bennée wrote:
> We all know the QEMU command line can become a fiendishly complex
> beast. Lets gently prepare our user for the horrors to come by
> referencing where other example command lines can be found in the
> manual.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
>   docs/system/quickstart.rst | 8 ++++++++
>   docs/system/targets.rst    | 2 ++
>   2 files changed, 10 insertions(+)
> 
> diff --git a/docs/system/quickstart.rst b/docs/system/quickstart.rst
> index 3a3acab5e7..3498c5a29f 100644
> --- a/docs/system/quickstart.rst
> +++ b/docs/system/quickstart.rst
> @@ -11,3 +11,11 @@ Download and uncompress a PC hard disk image with Linux installed (e.g.
>      |qemu_system| linux.img
>   
>   Linux should boot and give you a prompt.
> +
> +Users should be aware the above example elides a lot of the complexity
> +of setting up a VM with x86_64 specific defaults and an assumption the
"and assumes the ...", like Thomas says.

> +first non switch argument is a PC compatible disk image with a boot
> +sector. For non-x86 system where we emulate a broad range of machine

Either "For a non-x86 system ..." or "For non-x86 systems ..."

> +types the command lines are generally more explicit in defining the

You need a comma between "machine types" and "the".

> +machine and boot behaviour. You will find more example command lines
> +in the :ref:`system-targets-ref` section of the manual.

Reviewed-by: John Snow <jsnow@redhat.com>



      parent reply	other threads:[~2021-03-03 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 11:27 [RFC PATCH] docs/system: add a gentle prompt for the complexity to come Alex Bennée
2021-03-02  5:25 ` Thomas Huth
2021-03-03 17:55 ` Stefan Hajnoczi
2021-03-03 18:41 ` John Snow [this message]

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=eb5cc2cd-111d-84ea-910d-42aedfceef2f@redhat.com \
    --to=jsnow@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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.