All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Tomohiro Kusumi <kusumi.tomohiro@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"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 23:50:58 +0100	[thread overview]
Message-ID: <CALjAwxje2p3LGUWvEcMvQMH=EH_7wcTWGPzSOibr1ZmW3p1Fog@mail.gmail.com> (raw)
In-Reply-To: <CAHndrBm96oiGqS4FOcRh0doToaptqhQPHnArMaLJX_AUiyXVLw@mail.gmail.com>

Hi,

I'm very slowly working on improving the Sphinx generated man page.
The latest round of updates was partially to try and add any missing
sections that were only in the man page and weren't in the HOWTO.

There's still work to do as the "generated" man page doesn't have
typical man page section headings, it is missing key sections like
SYNTAX, it repeats the AUTHOR section twice etc. There are also a lot of
options that are missing their default values.

Other improvements need to be made to Sphinx itself: it seems to output
a UTF-8 man page that some platforms (macOS/OSX) struggle
with so it could do with an option to just output plain ASCII man
pages. Additionally some of the rendering looks a bit strange
(underlines only seem to go under letters, meta variable names after
parameters not underlined) and a few other oddities
like that.

On 4 July 2017 at 20:33, Tomohiro Kusumi <kusumi.tomohiro@gmail.com> 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).
>
> I simply don't know high-level documentation tools that this was the only way.
> (The current man page also seems to have been written by hand)
>
>
> 2017-07-04 22:03 GMT+03:00 Sitsofe Wheeler <sitsofe@gmail.com>:
>> Hi,
>>
>> On 4 July 2017 at 19:08,  <kusumi.tomohiro@gmail.com> wrote:
>>>
>>> This commit brings in updates from HOWTO. The exception is --debug
>>> option, which is too verbose yet not that important for all debug types
>>> to be listed in details.
>>
>> I've got to take my hat off to you Tomohiro - I thought it was
>> difficult enough to update just the HOWTO in the first place. Your
>> Herculean effort here brings the two more into sync!
>>
>> I'm secretly jealous of your productivity... Plus you've set back my
>> covert plan to make the current fio man page so useless that we switch
>> to having it built from HOWTO (using make -C doc man ) via Sphinx :-).

-- 
Sitsofe | http://sucs.org/~sits/


  parent reply	other threads:[~2017-07-04 22:50 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 [this message]
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='CALjAwxje2p3LGUWvEcMvQMH=EH_7wcTWGPzSOibr1ZmW3p1Fog@mail.gmail.com' \
    --to=sitsofe@gmail.com \
    --cc=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 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.