discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Michael Stapelberg <stapelberg@debian.org>
To: discuss@mandoc.bsd.lv
Subject: Re: In HTML output literal blocks should strip newline before closing pre
Date: Mon, 26 Oct 2020 14:42:12 +0100	[thread overview]
Message-ID: <CANnVG6mjUG1q5Z19w+Q7fvxdmdNrNyMQk6btSZ5QFQYBi=m=Kg@mail.gmail.com> (raw)
In-Reply-To: <20201026132653.GB62142@athene.usta.de>

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

That sounds reasonable! Thanks for sharing your plans.

On Mon, Oct 26, 2020 at 2:27 PM Ingo Schwarze <schwarze@usta.de> wrote:

> Hi Michael,
>
> Michael Stapelberg wrote on Sun, Oct 25, 2020 at 09:45:56PM +0100:
>
> > Ingo, would you be willing to cut a new release anytime soon?
>
> Yes, i have been eager to do that for quite some time already.
>
> > There have been a number of fixes, I think, that have not yet made
> > it into any release version.
>
> There are still two holdups that i'm trying to get out of the way:
>
>  1. A fuzzing run found a number of crashes, mostly assertion
>     failures and NULL pointer accesses.  Most of these have already
>     been fixed, but there is still a small number that need to be
>     investigated.  I want to finish that before release because
>     i do not want to make a release containing known bugs.
>
>  2. Unfortunately, the GNU troff project
>       https://www.gnu.org/software/groff/
>     made the decision to also roll a release *right now*, and the
>     last release of groff was also two years ago, so quite a few
>     thinks changed over there, too, and there is some fallout to
>     be dealt with.  Since i'm maintaining the groff port in OpenBSD
>     and since i'm also a groff developer, i must make sure nothing
>     goes wrong with that, which is draining some of my time that i
>     would like to spend on fixing the last few issues found in the
>     mandoc fuzzer run.
>
> But we will be getting there...
>
> Yours,
>   Ingo
> --
>  To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
>
>

-- 
Best regards,
Michael

[-- Attachment #2: Type: text/html, Size: 2297 bytes --]

      reply	other threads:[~2020-10-26 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 20:48 Aman Verma
2020-10-16 17:46 ` Ingo Schwarze
2020-10-25 20:45   ` Michael Stapelberg
2020-10-26 13:26     ` Ingo Schwarze
2020-10-26 13:42       ` Michael Stapelberg [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='CANnVG6mjUG1q5Z19w+Q7fvxdmdNrNyMQk6btSZ5QFQYBi=m=Kg@mail.gmail.com' \
    --to=stapelberg@debian.org \
    --cc=discuss@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).