From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: mandoc_char(7): don;t point to groff(1)
Date: Thu, 28 Oct 2010 19:15:11 +0100 [thread overview]
Message-ID: <20101028181535.GL14911@kerhand.co.uk> (raw)
imade this change after ingo zapped groff from openbsd base. i'm not
sure if you want it or not, but note that the mdoc(7) page talks about
"groff", not "groff(1)", so i thought it'd be fine.
or do we have to keep it as a local change?
jmc
Index: mandoc_char.7
===================================================================
RCS file: /cvs/src/share/man/man7/mandoc_char.7,v
retrieving revision 1.5
diff -u -r1.5 mandoc_char.7
--- mandoc_char.7 14 May 2010 15:03:01 -0000 1.5
+++ mandoc_char.7 28 Oct 2010 18:13:33 -0000
@@ -516,8 +516,7 @@
.Sh COMPATIBILITY
This section documents compatibility of
.Nm
-with older or existing versions of
-.Xr groff 1 .
+with older or existing versions of groff.
.Pp
The following render differently in
.Fl T Ns Ar ascii
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2010-10-28 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 18:15 Jason McIntyre [this message]
2010-10-29 0:10 ` Ingo Schwarze
2010-10-29 0:12 ` Kristaps Dzonsons
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=20101028181535.GL14911@kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--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).