From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: nested .RS/.RE is becoming more important
Date: Sat, 21 May 2011 17:38:18 -0400 (EDT) [thread overview]
Message-ID: <201105212138.p4LLcI24017577@krisdoz.my.domain> (raw)
Log Message:
-----------
nested .RS/.RE is becoming more important
Modified Files:
--------------
mdocml:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/TODO,v
retrieving revision 1.106
retrieving revision 1.107
diff -LTODO -LTODO -u -p -r1.106 -r1.107
--- TODO
+++ TODO
@@ -120,6 +120,8 @@
- .RS/.RE can be nested, see e.g. the x11/fluxbox manuals
noticed by dcoppa@ Wed, Apr 13, 2011 at 04:58:14PM +0200:
+ also affects p5-Net-SFTP-Foreign-1.65
+ as reported by gsoares@ Wed, 18 May 2011 09:59:06 -0300
- groff an-ext.tmac macros (.UR, .UE) occur in xine(5)
reported by brad@ Sat, 15 Jan 2011 15:45:23 -0500
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2011-05-21 21:38 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=201105212138.p4LLcI24017577@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).