From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>,
Jason McIntyre <jmc@cava.myzen.co.uk>,
Tim van der Molen <tbvdm@xs4all.nl>
Subject: Re: clean up date handling
Date: Mon, 07 Mar 2011 00:51:52 +0100 [thread overview]
Message-ID: <4D741E18.6000903@bsd.lv> (raw)
In-Reply-To: <20110305192749.GH27137@iris.usta.de>
On 05/03/2011 20:27, Ingo Schwarze wrote:
> 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.
Ingo,
I like these changes very much---I remember writing the date code in the
first versions of mandoc and being very puzzled with the canonical
format (hint: there is none).
I do feel that a "canonical" date format (or set of formats, e.g.,
YYYY-MM-DD, YYYY-MM, YYYY) should be suggested just so that people have
some direction, I agree that warning about it is superfluous.
So please check this in; when the code is committed I'll give it a
closer look-over and we can go from there.
Thanks again,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-03-06 23:52 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
2011-03-06 23:51 ` Kristaps Dzonsons [this message]
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=4D741E18.6000903@bsd.lv \
--to=kristaps@bsd.lv \
--cc=jmc@cava.myzen.co.uk \
--cc=schwarze@usta.de \
--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).