From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 2/2] NVMe-CLI : WDC-Plugin Documentation for Updated Smart Log Command
Date: Tue, 28 Nov 2017 08:47:25 -0700 [thread overview]
Message-ID: <20171128154724.GA11758@localhost.localdomain> (raw)
In-Reply-To: <20171128142955.9747-1-jeff.lien@wdc.com>
I'm going to have to split out the txt part from the autogenerated
files. Those are harder to merge when conflict arise, so I think it'd be
easier to just update documentation through the txt files and I'll
periodically regenerate as needed.
All are applied, will push later today if no objections to changing the
name to your sub-command.
next prev parent reply other threads:[~2017-11-28 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 14:29 [PATCH 2/2] NVMe-CLI : WDC-Plugin Documentation for Updated Smart Log Command Jeff Lien
2017-11-28 15:47 ` Keith Busch [this message]
2017-11-28 16:24 ` Jeffrey Lien
2017-11-29 16:38 ` Keith Busch
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=20171128154724.GA11758@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