From: hch@lst.de (Christoph Hellwig)
Subject: nvme-cli: Plea for help to document fabrics commands
Date: Fri, 23 Sep 2016 05:28:31 +0200 [thread overview]
Message-ID: <20160923032831.GA31423@lst.de> (raw)
In-Reply-To: <1474568868.15303.22.camel@linux.intel.com>
This has been on my TODO list for a while..
I'll wait for you to finish discover and will do the rest after that
as I think we can reuse a lot of the discover documentaiton for connect
and connect-all.
prev parent reply other threads:[~2016-09-23 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 18:27 nvme-cli: Plea for help to document fabrics commands J Freyensee
2016-09-23 3:28 ` Christoph Hellwig [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=20160923032831.GA31423@lst.de \
--to=hch@lst.de \
/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.