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, kristaps@bsd.lv
Subject: Re: [texi2mdoc] Documents without @node
Date: Tue, 13 Nov 2018 11:07:48 -0800	[thread overview]
Message-ID: <CAGw6cBvVxUVEyp10uKPwaKFuFYg+YCxvLvOrGB2k6ypBD7g0zw@mail.gmail.com> (raw)
In-Reply-To: <20181113102539.GE82487@athene.usta.de>

On 2018-11-13, Ingo Schwarze <schwarze@usta.de> wrote:
> Log Message:
> -----------
> If "@node Top" is missing, assume the document starts at "@top".
> For example, this occurs in ffmpeg(1).
> Issue reported and workaround proposed
> by Michael Forney <mforney at mforney dot org>.

Perfect, thanks! I can confirm that this fixes the issue with ffmpeg.texi.
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

      reply	other threads:[~2018-11-13 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  1:23 Michael Forney
2018-11-13  9:13 ` Ingo Schwarze
2018-11-13 10:25 ` Ingo Schwarze
2018-11-13 19:07   ` Michael Forney [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=CAGw6cBvVxUVEyp10uKPwaKFuFYg+YCxvLvOrGB2k6ypBD7g0zw@mail.gmail.com \
    --to=mforney@mforney.org \
    --cc=kristaps@bsd.lv \
    --cc=schwarze@usta.de \
    --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).