* nvme-cli documentation question
@ 2016-06-08 13:10 Christoph Hellwig
2016-06-08 14:52 ` Keith Busch
0 siblings, 1 reply; 2+ messages in thread
From: Christoph Hellwig @ 2016-06-08 13:10 UTC (permalink / raw)
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* nvme-cli documentation question
2016-06-08 13:10 nvme-cli documentation question Christoph Hellwig
@ 2016-06-08 14:52 ` Keith Busch
0 siblings, 0 replies; 2+ messages in thread
From: Keith Busch @ 2016-06-08 14:52 UTC (permalink / raw)
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-06-08 14:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-08 13:10 nvme-cli documentation question Christoph Hellwig
2016-06-08 14:52 ` Keith Busch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox