From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: must ignore \h with quoted argument
Date: Sun, 4 Dec 2011 19:41:41 -0500 (EST) [thread overview]
Message-ID: <201112050041.pB50ffea010109@krisdoz.my.domain> (raw)
Log Message:
-----------
must ignore \h with quoted argument
Modified Files:
--------------
mdocml:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/TODO,v
retrieving revision 1.125
retrieving revision 1.126
diff -LTODO -LTODO -u -p -r1.125 -r1.126
--- TODO
+++ TODO
@@ -30,6 +30,11 @@
--- missing roff features ----------------------------------------------
+- The pod2man preamble wants \h'...' with quoted numerical arguments,
+ see for example AUTHORS in MooseX::Getopt.3p, p5-MooseX-Getopt.
+ reported by Andreas Voegele <mail at andreasvoegele dot com>
+ Tue, 22 Nov 2011 15:34:47 +0100 on ports@
+
- .if n \{
.br\}
should cause an extra space to be raised.
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2011-12-05 0:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201112050041.pB50ffea010109@krisdoz.my.domain \
--to=schwarze@mdocml.bsd.lv \
--cc=source@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).