From: Ingo Schwarze <schwarze@usta.de>
To: Michael Forney <mforney@mforney.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: [texi2mdoc] [PATCH] Use mtime of input file for date, and allow override from command-line
Date: Tue, 13 Nov 2018 10:20:03 +0100 [thread overview]
Message-ID: <20181113092003.GD82487@athene.usta.de> (raw)
In-Reply-To: <CAGw6cBsR7iiWYPoPO3CUPb3G3EAid5bWy4sFn_Mf-nWQn5sRvg@mail.gmail.com>
Hi Micheal,
Michael Forney wrote on Tue, Nov 13, 2018 at 01:12:47AM -0800:
> Just personally in my build scripts for ffmpeg
I see.
> They use a bundled texi2pod.pl from gcc, followed by pod2man
> to generate the manuals, and they are not pre-generated in
> the source tar.
Yikes.
At some point, texi2mdoc(1) might also help them upstream,
but it is not yet mature enough to be advertised, and very
little work is done on texi2mdoc(1) nowadays.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2018-11-13 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 1:00 Michael Forney
2018-11-13 8:50 ` Ingo Schwarze
2018-11-13 9:12 ` Michael Forney
2018-11-13 9:20 ` Ingo Schwarze [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=20181113092003.GD82487@athene.usta.de \
--to=schwarze@usta.de \
--cc=mforney@mforney.org \
--cc=tech@mandoc.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).