tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Michael Forney <mforney@mforney.org>
To: Ingo Schwarze <schwarze@usta.de>
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 01:12:47 -0800	[thread overview]
Message-ID: <CAGw6cBsR7iiWYPoPO3CUPb3G3EAid5bWy4sFn_Mf-nWQn5sRvg@mail.gmail.com> (raw)
In-Reply-To: <20181113085046.GB82487@athene.usta.de>

On 2018-11-13, Ingo Schwarze <schwarze@usta.de> wrote:
> Hi Michael,
>
> Michael Forney wrote on Mon, Nov 12, 2018 at 05:00:13PM -0800:
>
>> I'm using texi2mdoc to generate ffmpeg manuals,
>
> Just personally, or are you somehow affiliated with the ffmpeg
> project (beyond sending occasional patches) and is that project
> considering to use texi2mdoc(1)?

Just personally in my build scripts for ffmpeg to avoid a build-time
dependency on perl. 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.

>> This patch changes texi2mdoc to use the mtime of the input file if
>> given by name, falling back to the current time if reading from stdin
>> or stat fails. In either case, the date can be given explicitly with
>> the -d flag.
>
> I agree, that's the right thing too do, pod2mdoc(1) behaves in a
> similar way.
>
> So i committed your patch with minimal tweaks (sorting headers,
> sorting stack variables roughly by size, making the manual page
> more similar too pod2mdoc(1)), also tweaking two nits while here:
> %F was the wrong format for mdoc(7), and the usage string lacked
> blanks between option letters and option arguments.

Great, thank you!
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

  reply	other threads:[~2018-11-13  9:12 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 [this message]
2018-11-13  9:20     ` Ingo Schwarze

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=CAGw6cBsR7iiWYPoPO3CUPb3G3EAid5bWy4sFn_Mf-nWQn5sRvg@mail.gmail.com \
    --to=mforney@mforney.org \
    --cc=schwarze@usta.de \
    --cc=tech@mandoc.bsd.lv \
    --subject='Re: [texi2mdoc] [PATCH] Use mtime of input file for date, and allow override from command-line' \
    /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

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).