discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Jason McIntyre <jmc@kerhand.co.uk>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mandoc_char(7): don;t point to groff(1)
Date: Fri, 29 Oct 2010 02:10:01 +0200	[thread overview]
Message-ID: <20101029001001.GI7102@iris.usta.de> (raw)
In-Reply-To: <20101028181535.GL14911@kerhand.co.uk>

Hi Jason,

Jason McIntyre wrote on Thu, Oct 28, 2010 at 07:15:11PM +0100:

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

Right, Kristaps has already systematically removed all groff Xrs
from the mandoc manuals, but this one was apparently overlooked,
see http://mdocml.bsd.lv/cgi-bin/cvsweb/mdoc.7?cvsroot=mdocml
revision 1.148.

So i have commited this one to bsd.lv right away.

Thanks,
  Ingo

> 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

  reply	other threads:[~2010-10-29  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 18:15 Jason McIntyre
2010-10-29  0:10 ` Ingo Schwarze [this message]
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=20101029001001.GI7102@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=jmc@kerhand.co.uk \
    /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).