From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH] ndctl/namespace: Fixup man page indentation
Date: Tue, 29 Oct 2019 20:18:47 +0000 [thread overview]
Message-ID: <96e83e44efe30efd8d599b89b3a117242ab860f2.camel@intel.com> (raw)
In-Reply-To: <157237178859.4146560.1913830646961375457.stgit@dwillia2-desk3.amr.corp.intel.com>
On Tue, 2019-10-29 at 10:56 -0700, Dan Williams wrote:
> Text that follows a list tends to continue the list indentation. Use a
> bare "::" to end the list indentation.
>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> Documentation/ndctl/ndctl-create-namespace.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ndctl/ndctl-create-namespace.txt b/Documentation/ndctl/ndctl-create-namespace.txt
> index 45a4c4c2f408..8cd80fa789c1 100644
> --- a/Documentation/ndctl/ndctl-create-namespace.txt
> +++ b/Documentation/ndctl/ndctl-create-namespace.txt
> @@ -155,7 +155,7 @@ OPTIONS
> per-page metadata. The allocation can be drawn from either:
> - "mem": typical system memory
> - "dev": persistent memory reserved from the namespace
> -
> +::
> Given relative capacities of "Persistent Memory" to "System
> RAM" the allocation defaults to reserving space out of the
> namespace directly ("--map=dev"). The overhead is 64-bytes per
>
Good find!
I see how this (ab)uses the list marker by creating a new list item
without a new 'term' associated with it. I disliked creating a new list
item when the paragraph logically belongs in the previous list, and I
tried to use various combinations of list continuation markers, play
around with list starts/ends, but couldn't get the paragraph to
dissociate from the 'dev/mem' sublist and associate it back to the
'parent' list.
So I'll take this :)
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
prev parent reply other threads:[~2019-10-29 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 17:56 [ndctl PATCH] ndctl/namespace: Fixup man page indentation Dan Williams
2019-10-29 20:18 ` Verma, Vishal L [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=96e83e44efe30efd8d599b89b3a117242ab860f2.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.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