All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 1/1] doc: correct Vhost Sample Application guide
Date: Wed, 9 Dec 2015 14:50:58 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023FFEB4@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1449664541-9546-1-git-send-email-bernard.iremonger@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bernard Iremonger
> Sent: Wednesday, December 9, 2015 12:36 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 1/1] doc: correct Vhost Sample Application
> guide
> 
> correct sample console commands
> 
> Fixes: d0dff9ba445e ("doc: sample application user guide"
> Fixes: 9bc23cb8209c ("doc: add vhost-user to sample guide")
> Fixes: 43866bf71d58 ("doc: fix vhost sample parameter")
> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> ---
>  doc/guides/sample_app_ug/vhost.rst | 40 +++++++++++++++++++--------------
>
> ...
> 
>      Redistribution and use in source and binary forms, with or without @@
> -386,13 +386,13 @@ Running the Sample Code
> 
>      .. code-block:: console
> 
> -        user@target:~$ ./build/app/vhost-switch -c f -n 4 --huge-dir /


Also, as a general note, not just to this document/patch.

I don't think the "user@target:~$" prefixes used in some DPDK
Doc commandlines is useful.

It prevents a straight copy and paste for testing, it makes the
literal block lines longer than they should be, it isn't used
consistently everywhere, it is visually distracting (in some
cases it is longer than the command being shown), and it isn't
always correct (I presume in the above case of "user@target" you
would need run the application as sudo if you are a non root
user).

Any objections to removing these as documents are updated?


John

  parent reply	other threads:[~2015-12-09 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 12:35 [PATCH 1/1] doc: correct Vhost Sample Application guide Bernard Iremonger
2015-12-09 13:36 ` Xie, Huawei
2015-12-09 14:43 ` Mcnamara, John
2015-12-09 16:10   ` Iremonger, Bernard
2015-12-09 14:50 ` Mcnamara, John [this message]
2015-12-09 15:09   ` Thomas Monjalon
2015-12-09 16:14     ` Iremonger, Bernard
2015-12-10  6:40       ` Yuanhan Liu
2015-12-09 17:18 ` [PATCH v2 " Bernard Iremonger
2015-12-10  6:52   ` Yuanhan Liu
2015-12-10  9:58     ` Iremonger, Bernard
2015-12-10 12:10       ` Xie, Huawei
2015-12-10 13:19         ` Iremonger, Bernard
2015-12-10 13:33           ` Xie, Huawei
2015-12-10 11:23   ` [PATCH v3] " Bernard Iremonger
2015-12-14  0:23     ` Thomas Monjalon

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=B27915DBBA3421428155699D51E4CFE2023FFEB4@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.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 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.