From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/5] doc: man page cleanup
Date: Sat, 22 May 2021 19:33:41 -0300 [thread overview]
Message-ID: <87r1hys8je.fsf@tethera.net> (raw)
In-Reply-To: <874keuwh2r.fsf@nikula.org>
Jani Nikula <jani@nikula.org> writes:
> On Sat, 22 May 2021, David Bremner <david@tethera.net> wrote:
>> Jani Nikula <jani@nikula.org> writes:
>>
>>> I saw [1] and decided to give it some love. :)
>>>
>>> Mostly this is all about adding html cross-references all over the place
>>> while trying to keep the roff man pages roughly the same. Also updating
>>> the man page rst becomes easier by setting a clean example.
>>>
>>> BR,
>>> Jani.
>>>
>>
>> Series LGTM, based on a bit of sampling of the outputs. I did wonder
>> if the FILES section in notmuch-config should also move to notmuch(1). I
>> can see arguments for both options.
>
> I was wondering about that myself. Should I respin with that?
>
Either that or an addon to the series, whatever is easiest.
d
next prev parent reply other threads:[~2021-05-22 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 20:44 [PATCH 0/5] doc: man page cleanup Jani Nikula
2021-05-21 20:44 ` [PATCH 1/5] doc: use manpage role references to external man pages Jani Nikula
2021-05-21 20:44 ` [PATCH 2/5] doc: cross-reference notmuch man pages with actual links Jani Nikula
2021-05-21 20:44 ` [PATCH 3/5] doc: use envvar directive and role for environment variables Jani Nikula
2021-05-21 20:44 ` [PATCH 4/5] doc: use program and option directives to document options Jani Nikula
2021-05-21 20:44 ` [PATCH 5/5] doc: example command-line option reference Jani Nikula
2021-05-22 19:51 ` [PATCH 0/5] doc: man page cleanup David Bremner
2021-05-22 22:15 ` Jani Nikula
2021-05-22 22:33 ` David Bremner [this message]
2021-05-22 22:56 ` Jani Nikula
2021-05-22 23:43 ` David Bremner
2021-05-23 11:13 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1hys8je.fsf@tethera.net \
--to=david@tethera.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).