From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Re: groff-1.20.1 patches for automatic comparisons
Date: Tue, 25 Jan 2011 15:27:02 +0100 [thread overview]
Message-ID: <20110125142702.GI65811@acme.spoerlein.net> (raw)
In-Reply-To: <20110124153926.GC16282@iris.usta.de>
On Mon, 24.01.2011 at 16:39:26 +0100, Ingo Schwarze wrote:
> Hi,
>
> just for your information, in case you are doing automatic comparisons
> of groff and mandoc output, here is the current version of the OpenBSD
> groff-1.20.1 port i am using. Even if you are not using OpenBSD, the
> patches might be interesting. In particular,
> groff/patches/patch-src_roff_troff_env_cpp
Exactly what kinds of adjustments is this disabling?
> groff/patches/patch-tmac_doc_tmac
> groff/patches/patch-tmac_troffrc
> help a lot.
Thanks, very useful tweaks.
Also, why are you patching doc-common and not simply using overrides in
mdoc.local?
Cheers,
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-01-25 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 15:39 Ingo Schwarze
2011-01-25 14:27 ` Ulrich Spörlein [this message]
2011-01-26 19:24 ` 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=20110125142702.GI65811@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--cc=discuss@mdocml.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).