From: keith.busch@intel.com (Keith Busch)
Subject: nvme-cli documentation updates
Date: Wed, 12 Oct 2016 15:23:30 -0400 [thread overview]
Message-ID: <20161012192329.GA12827@localhost.localdomain> (raw)
In-Reply-To: <1476261953-23119-1-git-send-email-hch@lst.de>
On Wed, Oct 12, 2016@10:45:50AM +0200, Christoph Hellwig wrote:
> [third try, I'm really got as using the wrong list address today. Sorry Jay.. :)]
>
> This series improves the nvme-discover manpage a bit, and adds a new
> one for nvme-connect-all. I would have preferred to share a page for
> both commands as there is a lot of duplication, but I couldn't find a way
> to do that.
I applied them all and regenerated the man and html pages. I had to make
one minor change to connect-all.txt to get asciidoc to understand the
header portion.
I had to fixup the multipart conent type in patches 2/3 and 3/3, and
missed J's comments while doing that. I'll apply updates on top of the
current master if we need to change any wording.
prev parent reply other threads:[~2016-10-12 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 8:45 nvme-cli documentation updates Christoph Hellwig
2016-10-12 8:45 ` [PATCH 1/3] consolidate reporting bugs information Christoph Hellwig
2016-10-12 17:13 ` J Freyensee
2016-10-12 8:45 ` [PATCH 2/3] fine tune the nvme-discover manpage Christoph Hellwig
2016-10-12 17:18 ` J Freyensee
2016-10-13 10:26 ` Christoph Hellwig
2016-10-13 16:43 ` J Freyensee
2016-10-12 8:45 ` [PATCH 3/3] add documentation for the connect-all command Christoph Hellwig
2016-10-12 17:21 ` J Freyensee
2016-10-13 10:27 ` Christoph Hellwig
2016-10-12 19:23 ` Keith Busch [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=20161012192329.GA12827@localhost.localdomain \
--to=keith.busch@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox