Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Vincent Fu <vincent.fu@samsung.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"martin.steigerwald@proact.de" <martin.steigerwald@proact.de>,
	"sandeen@redhat.com" <sandeen@redhat.com>
Subject: RE: [PATCH] docs: generate manpage from README and HOWTO
Date: Wed, 2 Mar 2022 15:27:03 +0000	[thread overview]
Message-ID: <41bcb630c61d4ecd965654d328e95c96@samsung.com> (raw)
In-Reply-To: <20220302152122.64596-1-vincent.fu@samsung.com>

> -----Original Message-----
> From: Vincent Fu
> Sent: Wednesday, March 2, 2022 10:22 AM
> To: fio@vger.kernel.org; axboe@kernel.dk; martin.steigerwald@proact.de;
> sandeen@redhat.com
> Cc: Vincent Fu <vincent.fu@samsung.com>
> Subject: [PATCH] docs: generate manpage from README and HOWTO
> 
> We have a longstanding problem where fio documentation updates must be
> made to both the HOWTO and manpage.
> 
> Here is a solution that generates a manpage from the README and HOWTO
> using Sphinx.
> 
> The downside to being able to maintain only one version of the
> documentation is that this will cause a bit of trouble for those who package
> fio and users building fio without Sphinx support will no longer have a
> manpage.
> 
> Does this seem like a reasonable tradeoff? If so, I will follow up with patches
> to remove the original manpage and update the Sphinx-generated manpage
> to have the standard NAME, SYNOPSIS, DESCRIPTION, etc layout.
> 

Oops, this was intended to be a RFC.

  reply	other threads:[~2022-03-02 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220302152331uscas1p297d64e27b29db799fd64d494ad584860@uscas1p2.samsung.com>
2022-03-02 15:22 ` [PATCH] docs: generate manpage from README and HOWTO Vincent Fu
2022-03-02 15:27   ` Vincent Fu [this message]
2022-03-02 18:49     ` Nick Neumann
2022-03-07 13:35   ` Jens Axboe

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=41bcb630c61d4ecd965654d328e95c96@samsung.com \
    --to=vincent.fu@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=martin.steigerwald@proact.de \
    --cc=sandeen@redhat.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