From: keith.busch@intel.com (Keith Busch)
Subject: nvme-cli documentation question
Date: Wed, 8 Jun 2016 10:52:42 -0400 [thread overview]
Message-ID: <20160608145241.GC1430@localhost.localdomain> (raw)
In-Reply-To: <20160608131036.GA10503@infradead.org>
On Wed, Jun 08, 2016@06:10:36AM -0700, Christoph Hellwig wrote:
> It seems like nvme-cli generate the html and man page version of the
> documentation from the .txt files. Any reason the generated files
> are checked in? How are they generated, and how is the process for
> them handled?
While I wouldn't mind having only the .txt, the build artifacts are
committed to version control because some people using this project
couldn't install asciidoc to generate the man pages, so they're included
for convenience.
prev parent reply other threads:[~2016-06-08 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 13:10 nvme-cli documentation question Christoph Hellwig
2016-06-08 14:52 ` 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=20160608145241.GC1430@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 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.