Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Tomohiro Kusumi <kusumi.tomohiro@gmail.com>
Cc: Sitsofe Wheeler <sitsofe@gmail.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>,
	Tomohiro Kusumi <tkusumi@tuxera.com>
Subject: Re: [PATCH 1/7] man: sync OPTIONS section with HOWTO
Date: Tue, 4 Jul 2017 16:08:36 -0600	[thread overview]
Message-ID: <20170704220834.GA15281@kernel.dk> (raw)
In-Reply-To: <CAHndrBm96oiGqS4FOcRh0doToaptqhQPHnArMaLJX_AUiyXVLw@mail.gmail.com>

On Tue, Jul 04 2017, Tomohiro Kusumi wrote:
> Hi
> 
> Thanks.
> I think it's better if there's a way to somehow automatically generate
> the man page from HOWTO like you mentioned (and update from that).

Yes, that should definitely be the long term goal. It's pretty annoying
to have to update both, hence people forget (even me), and then they
drift again.

Thankfully people are working on that :-)

-- 
Jens Axboe



  reply	other threads:[~2017-07-04 22:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 18:08 [PATCH 0/7] Sync fio(1) man page with HOWTO kusumi.tomohiro
2017-07-04 18:08 ` [PATCH 1/7] man: sync OPTIONS section " kusumi.tomohiro
2017-07-04 19:03   ` Sitsofe Wheeler
2017-07-04 19:33     ` Tomohiro Kusumi
2017-07-04 22:08       ` Jens Axboe [this message]
2017-07-04 22:09       ` Jens Axboe
2017-07-04 22:50       ` Sitsofe Wheeler
2017-07-04 18:08 ` [PATCH 2/7] man: sync "JOB FILE FORMAT" " kusumi.tomohiro
2017-07-04 18:08 ` [PATCH 3/7] man: sync "JOB FILE PARAMETERS" " kusumi.tomohiro
2017-07-04 18:08 ` [PATCH 4/7] man: sync "PARAMETER TYPES" " kusumi.tomohiro
2017-07-04 18:08 ` [PATCH 5/7] man: refer to REPORTING-BUGS for bug reporting kusumi.tomohiro
2017-07-04 18:08 ` [PATCH 6/7] HOWTO: minor backports from the man page kusumi.tomohiro
2017-07-04 18:08 ` [PATCH 7/7] HOWTO: fix indentation for options and job parameters kusumi.tomohiro
2017-07-04 22:09 ` [PATCH 0/7] Sync fio(1) man page with HOWTO 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=20170704220834.GA15281@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=kusumi.tomohiro@gmail.com \
    --cc=sitsofe@gmail.com \
    --cc=tkusumi@tuxera.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