All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: add xenstore-ls man page
Date: Tue, 2 Jul 2013 11:38:47 +0100	[thread overview]
Message-ID: <51D2ADB7.9070900@citrix.com> (raw)
In-Reply-To: <1372760870.27768.78.camel@zakaz.uk.xensource.com>

On 02/07/13 11:27, Ian Campbell wrote:
> On Tue, 2013-07-02 at 11:21 +0100, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> 
> Cool, thanks.
> 
> Any reason not to do the others? (I'll assume lack of time...)

xenstore-ls -p output was confusing me and it probably confuses lots of
people.

I've not got around to the other pages yet.

> xenstore-ls is actually a pointer to the multifunction xenstore client
> utility (i.e. you can run "xenstore ls ..." too).
>
> Is the normal Unix idiom in this case to have a single manpage which
> documents all the various sub-functions.

man does the right thing.  Both "man xenstore-ls" and "man xenstore ls"
will get this man page.

I think its best to have separate pages for each (sub)utility -- keeps
each page short and free of clutter.  This is how the git man pages are
done.

> BTW I'm not suggesting you write them all but perhaps a single
> xenstore.pod.1 with placeholders for the others would be a better start?

An additional xenstore(1) man page summarizing the sub-commands would be
useful.  Again, ala git.

I'll work on this and the pages for the other xenstore utilities later,
when I have more time.

David

  reply	other threads:[~2013-07-02 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 10:21 [PATCH] docs: add xenstore-ls man page David Vrabel
2013-07-02 10:27 ` Ian Campbell
2013-07-02 10:38   ` David Vrabel [this message]
2013-07-02 10:41     ` Ian Campbell
2013-07-03  7:38 ` Matthew Daley
2013-07-03  9:29   ` David Vrabel
2013-07-03  9:33     ` Ian Campbell

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=51D2ADB7.9070900@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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.