tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Jason McIntyre <jmc@cava.myzen.co.uk>
Cc: tech@mdocml.bsd.lv, Tim van der Molen <tbvdm@xs4all.nl>
Subject: Re: clean up date handling
Date: Sat, 5 Mar 2011 20:27:49 +0100	[thread overview]
Message-ID: <20110305192749.GH27137@iris.usta.de> (raw)
In-Reply-To: <20110305075314.GC18361@harkle.bramka>

Hi Jason,

Jason McIntyre wrote on Sat, Mar 05, 2011 at 07:52:50AM +0001:
> On Sat, Mar 05, 2011 at 01:15:40AM +0100, Ingo Schwarze wrote:

[...]
>> +Other arguments are not portable; the
>> +.Xr mandoc 1
>> +utility handles them as follows:
>> +.Bl -dash -offset 3n -compact
>> +.It
>> +To have the date automatically filled in by
>>  .Xr cvs 1 ,
>> -or instead a valid canonical date as specified by
>> -.Sx Dates .
>> -If a date does not conform or is empty, the current date is used.
>> +the special string
>> +.Dq $\&Mdocdate$
>> +can be given as an argument.

> shouldn;t you mention this is openbsd only?

Yes, that makes sense.
However, it's just OpenBSD's cvs(1) that is special,
mandoc(1) can handle $Mdocdate$ on any platform,
so i will use this wording:

  To have the date automatically filled in by the
  .Ox
  version of
  .Xr cvs 1 ,
  the special string
  .Dq $\&Mdocdate$
  can be given as an argument.

I have fixed your other findings in my tree, so if this goes in,
they will be contained.

Thanks,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2011-03-05 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  0:14 Ingo Schwarze
2011-03-04 22:24 ` Ingo Schwarze
2011-03-05  0:15   ` Ingo Schwarze
     [not found]     ` <20110305075314.GC18361@harkle.bramka>
2011-03-05 19:27       ` Ingo Schwarze [this message]
2011-03-06 23:51         ` Kristaps Dzonsons

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=20110305192749.GH27137@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=jmc@cava.myzen.co.uk \
    --cc=tbvdm@xs4all.nl \
    --cc=tech@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).