Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: kusumi.tomohiro@gmail.com
Cc: fio@vger.kernel.org, Tomohiro Kusumi <tkusumi@tuxera.com>
Subject: Re: [PATCH 0/7] Sync fio(1) man page with HOWTO
Date: Tue, 4 Jul 2017 16:09:00 -0600	[thread overview]
Message-ID: <20170704220858.GB15281@kernel.dk> (raw)
In-Reply-To: <20170704180816.39585-1-tkusumi@tuxera.com>

On Tue, Jul 04 2017, kusumi.tomohiro@gmail.com wrote:
> From: Tomohiro Kusumi <tkusumi@tuxera.com>
> 
> The man page hasn't been in sync with many of the updates made for
> HOWTO. These commits update the man page based on what HOWTO has,
> where each commit corresponds to a single section (instead of updating
> with commit-to-commit basis). The man page being in sync with HOWTO
> also makes it easier to make changes, whenever HOWTO is updated in the
> future.
> 
> The goal is to be in sync with HOWTO without being too verbose for
> a man page. Note that they don't include contents that do not exist
> in HOWTO (i.e. I didn't newly create anything). Also note these are
> only beginning part of the man page.
> 
> These commits include
> 1. Import updates made only for HOWTO (diffs), unless the changes are
>    too long/verbose to be mentioned in the man page.
> 2. Replace the entire section or paragraph with the corresponding one
>    in HOWTO (partly as a result of 1), if these two are essencially
>    saying the same thing with small modification, so that we don't see
>    two different contents in two documents that are almost the same.
> 3. Make some small changes when above two are imported, such as using
>    directives, removal of double white spaces, removal of expressions
>    that don't fit in well with a man page (e.g. This section describes...).
> 4. Backport some small changes from the man page to HOWTO, which seem
>    to have been made when the man page was first introduced. These are
>    mostly minor fixups.

Thanks, applied.

-- 
Jens Axboe



      parent reply	other threads:[~2017-07-04 22:09 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
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 ` Jens Axboe [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=20170704220858.GB15281@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=kusumi.tomohiro@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