From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: [PATCH] .Bsx should print "BSD/OS" only
Date: Thu, 21 Oct 2010 10:24:40 +0200 [thread overview]
Message-ID: <20101021082440.GA55872@acme.spoerlein.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
Hi folks,
subject says it, groff does it, attached patch fixes it.
Please note, that there are manpages out there, that go like this:
This manual page was written by
[...]
with inspiration from BSDi's
.Bsx
.Xr elf 5
manpage.
And as you can see, having Bsx display BSDI again is rather redundant.
Thanks,
Uli
[-- Attachment #2: bsdos.diff --]
[-- Type: text/x-diff, Size: 956 bytes --]
Index: mdoc_html.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/mdoc_html.c,v
retrieving revision 1.111
diff -u -p -r1.111 mdoc_html.c
--- mdoc_html.c 10 Oct 2010 09:59:48 -0000 1.111
+++ mdoc_html.c 21 Oct 2010 08:21:29 -0000
@@ -843,7 +843,7 @@ mdoc_xx_pre(MDOC_ARGS)
switch (n->tok) {
case (MDOC_Bsx):
- pp = "BSDI BSD/OS";
+ pp = "BSD/OS";
break;
case (MDOC_Dx):
pp = "DragonFly";
Index: mdoc_term.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/mdoc_term.c,v
retrieving revision 1.193
diff -u -p -r1.193 mdoc_term.c
--- mdoc_term.c 10 Oct 2010 09:59:48 -0000 1.193
+++ mdoc_term.c 21 Oct 2010 08:21:29 -0000
@@ -1657,7 +1657,7 @@ termp_xx_pre(DECL_ARGS)
pp = NULL;
switch (n->tok) {
case (MDOC_Bsx):
- pp = "BSDI BSD/OS";
+ pp = "BSD/OS";
break;
case (MDOC_Dx):
pp = "DragonFly";
next reply other threads:[~2010-10-21 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 8:24 Ulrich Spörlein [this message]
2010-10-23 23:32 ` 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=20101021082440.GA55872@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).