source@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: kristaps@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Start putting in release notes.
Date: Thu, 22 Jul 2010 10:30:06 -0400 (EDT)	[thread overview]
Message-ID: <201007221430.o6MEU6en023011@krisdoz.my.domain> (raw)

Log Message:
-----------
Start putting in release notes.  A record is good because this release
will have lots of small, incremental improvements.

Modified Files:
--------------
    mdocml:
        index.sgml

Revision Data
-------------
Index: index.sgml
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/index.sgml,v
retrieving revision 1.85
retrieving revision 1.86
diff -Lindex.sgml -Lindex.sgml -u -p -r1.85 -r1.86
--- index.sgml
+++ index.sgml
@@ -296,6 +296,24 @@
 					</H1>
 					<DIV CLASS="news">
 						<P>
+							<SPAN CLASS="date">XX-07-2010</SPAN>:
+							version 1.10.5
+						</P>
+						<P>
+							Purely a bug-fix and polish release.  Highlights:
+						</P>
+						<UL>
+							<LI>fix <Q>Sm</Q> handling</LI>
+							<LI>fix end-of-sentence handling for embedded sentences</LI>
+							<LI>polish <A HREF="man.7.html">man</A> documentation</LI>
+							<LI>document all <A HREF="mdoc.7.html">mdoc</A> macros</LI>
+							<LI>polish <A HREF="mandoc.1.html">mandoc</A> -Tps output</LI>
+							<LI>lots of internal clean-ups in character escapes</LI>
+							<LI>un-break literal contexts in <A HREF="man.7.html">man</A> documents</LI>
+						</UL>
+					</DIV>
+					<DIV CLASS="news">
+						<P>
 							<SPAN CLASS="date">12-07-2010</SPAN>:
 							version 1.10.4
 						</P>
--
 To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv

                 reply	other threads:[~2010-07-22 14:30 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=201007221430.o6MEU6en023011@krisdoz.my.domain \
    --to=kristaps@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).