From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 6/8] doc lei: add manpages for new commands
Date: Sun, 28 Mar 2021 23:35:41 -0400 [thread overview]
Message-ID: <87pmzi7hte.fsf@kyleam.com> (raw)
In-Reply-To: <YGFImEcWX1mCJJwv@dcvr>
Eric Wong writes:
> Kyle Meyer <kyle@kyleam.com> wrote:
>> +=for comment
>
>> +TODO: The below options are shared with lei-q. Any good approaches to
>> +not repeating the text?
>
> I don't know about natively in POD. Perhaps just a list of
> switches and a pointer to lei-q(1)?
Yeah, this sounds like the way to go to me. I'll make a note to do it
for the next round.
Thanks.
next prev parent reply other threads:[~2021-03-29 3:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 3:11 [PATCH 0/8] doc: lei manpages, round 4 Kyle Meyer
2021-03-29 3:11 ` [PATCH 1/8] doc lei-q: fix typo in -tt description Kyle Meyer
2021-03-29 3:11 ` [PATCH 2/8] doc lei: note --stdin shortcut in synopses Kyle Meyer
2021-03-29 3:11 ` [PATCH 3/8] doc lei: drop an unnecessary to-do comment Kyle Meyer
2021-03-29 3:11 ` [PATCH 4/8] doc lei: don't render most to-do comments Kyle Meyer
2021-03-29 3:11 ` [PATCH 5/8] doc lei: update manpages with new options Kyle Meyer
2021-03-29 3:11 ` [PATCH 6/8] doc lei: add manpages for new commands Kyle Meyer
2021-03-29 3:25 ` Eric Wong
2021-03-29 3:35 ` Kyle Meyer [this message]
2021-03-29 3:11 ` [PATCH 7/8] doc lei overview: note that lei-init is usually unnecessary Kyle Meyer
2021-03-29 3:11 ` [PATCH 8/8] doc lei overview: better explain routes into local store Kyle Meyer
2021-03-29 3:18 ` [PATCH 0/8] doc: lei manpages, round 4 Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmzi7hte.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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://80x24.org/public-inbox.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).