discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Thomas Klausner <wiz@NetBSD.org>
To: discuss@mdocml.bsd.lv
Subject: Re: pod2mdoc: Release version 0.0.12.
Date: Fri, 11 Jul 2014 11:51:43 +0200	[thread overview]
Message-ID: <20140711095143.GA15450@danbala.tuwien.ac.at> (raw)
In-Reply-To: <201407110927.s6B9ROIx020476@krisdoz.my.domain>

That's good news!

In the process of updating pkgsrc, I saw one warning:
pod2mdoc.c: In function 'trylink':
pod2mdoc.c:184:14: warning: variable 'text' set but not used [-Wunused-but-set-variable]
  const char *text;
              ^

 Thomas

On Fri, Jul 11, 2014 at 05:27:24AM -0400, schwarze@mdocml.bsd.lv wrote:
> Log Message:
> -----------
> Release version 0.0.12.
> The LibReSSL Valhalla Rampage considers starting to use this
> for automatic manual conversion (sic! :) right now.
> 
> Modified Files:
> --------------
>     pod2mdoc:
>         Makefile
>         index.xml
> 
> Revision Data
> -------------
> Index: index.xml
> ===================================================================
> RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/pod2mdoc/index.xml,v
> retrieving revision 1.4
> retrieving revision 1.5
> diff -Lindex.xml -Lindex.xml -u -p -r1.4 -r1.5
> --- index.xml
> +++ index.xml
> @@ -56,7 +56,16 @@
>  				hasn't already been covered in the <a href="pod2mdoc.1.html">manual</a>.
>  			</p>
>  			<h2>
> -				New in version @VERSION@...
> +				New in version 0.0.12 (July 11, 2014)
> +			</h2>
> +			<p>
> +				Render <code>B&lt;NULL&gt;</code> as <code>.Dv NULL</code>.
> +				Correctly check the number of arguments.
> +				Show the usage() message if there are too many arguments.
> +				Mention the optional "file" argument in the usage() message.
> +			</p>
> +			<h2>
> +				New in version 0.0.11 (April 7, 2014)
>  			</h2>
>  			<p>
>  				Properly render <code>#include</code> in the SYNOPSIS with <code>In</code>.
> Index: Makefile
> ===================================================================
> RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/pod2mdoc/Makefile,v
> retrieving revision 1.9
> retrieving revision 1.10
> diff -LMakefile -LMakefile -u -p -r1.9 -r1.10
> --- Makefile
> +++ Makefile
> @@ -1,4 +1,4 @@
> -VERSION = 0.0.11
> +VERSION = 0.0.12
>  CFLAGS += -g -W -Wall -Wstrict-prototypes -Wno-unused-parameter -Wwrite-strings 
>  WWWPREFIX = /usr/vhosts/mdocml.bsd.lv/www/htdocs/pod2mdoc
>  
> --
>  To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
> 
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

       reply	other threads:[~2014-07-11  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sfid-H20140711-112733-+044.35-1@spamfilter.osbf.lua>
     [not found] ` <201407110927.s6B9ROIx020476@krisdoz.my.domain>
2014-07-11  9:51   ` Thomas Klausner [this message]
2014-07-11 10: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=20140711095143.GA15450@danbala.tuwien.ac.at \
    --to=wiz@netbsd.org \
    --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).