From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-2.sys.kth.se (smtp-2.sys.kth.se [130.237.32.160]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id o6QDixh0017258 for ; Mon, 26 Jul 2010 09:45:00 -0400 (EDT) Received: from smtp-2.sys.kth.se (localhost [127.0.0.1]) by smtp-2.sys.kth.se (Postfix) with ESMTP id A0D8814D7F4 for ; Mon, 26 Jul 2010 15:44:54 +0200 (CEST) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-2.sys.kth.se ([127.0.0.1]) by smtp-2.sys.kth.se (smtp-2.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kAlREnB1ipv0 for ; Mon, 26 Jul 2010 15:44:46 +0200 (CEST) X-KTH-Auth: kristaps [130.237.221.96] X-KTH-mail-from: kristaps@bsd.lv X-KTH-rcpt-to: discuss@mdocml.bsd.lv Received: from [130.237.221.96] (ctime.pdc.kth.se [130.237.221.96]) by smtp-2.sys.kth.se (Postfix) with ESMTP id 0B6BE14F131 for ; Mon, 26 Jul 2010 15:44:44 +0200 (CEST) Message-ID: <4C4D90CA.8010607@bsd.lv> Date: Mon, 26 Jul 2010 15:42:34 +0200 From: Kristaps Dzonsons User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707) X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 To: discuss@mdocml.bsd.lv Subject: Re: Opinions on .Dd? References: <4C4BBDE5.8020901@online.de> <20100725062509.GA22919@iris.usta.de> <4C4C292C.9020500@online.de> In-Reply-To: <4C4C292C.9020500@online.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sascha Wildner wrote: > On 7/25/2010 8:25, Ingo Schwarze wrote: >> Maybe porting Mdocdate to DragonFly cvs might help you: I think >> is solves exactly the problem you describe. I just checked on >> Linux, non-OpenBSD groff auto-detects pages containing Mdocdate >> as mdoc(7) and formats them nicely. I'm sorry i don't have a >> Solaris box and can't check there... > > Well, DragonFly uses git and afaik OpenBSD's way is implemented in rcs. > > Yeah supports as in "just takes today's date if the string makes no > sense to it". You can write .Dd foo or .Dd $Mdocdate$, doesn't matter. > mdocml seems to follow this convention. > > I guess the proper way of "nuking .Dd" would probably be to leave it in > but just "officially" don't care about it any longer, as in, don't > bother people any longer to update it and tell them "update it if you > like, but we don't require you to". And explicitly putting something > else there instead of a date (so the "today's date" default kicks in) > just to make that point seems silly too. > > Aside from the portability problems, deciding to remove it entirely also > would just shift the "I have to bother everyone to update it" problem to > "I have to bother everyone to remove it from imported manual pages", so > there is no big gain, even if removing it was portable. > > Believe it or not, it's already a comforting thought that others > sympathize. :) I think I have no opinion either way, although my first thought was "burn the witches!" "`Dd' forever!". Second thought: a manual date is in general ambiguous. What does it mean? Last edit time? Last checkin? And what does it matter, considering it usually can't be corroborated with corresponding binary (or whatever)? OpenBSD is the exception, as Mdocdate is used unilaterally. So I dug around and found that `Dd' accepts no arguments. It prints "Epoch" in place of a date (wtf?). I think an empty `Dd' is less ambiguous than a bogus date. (I'm now committing a fix to the effect that `Dd' can be empty.) Either way, the mdoc.7 manual explicitly states that only cvs(1) works with $Mdocdate$, so it's clear it won't work with svn or git. I'm happy with putting some notes to the extent of "Usage of the `Dd' field is usually one of convention" and listing that OpenBSD exclusively uses $Mdocdate$, whilst a general-purpose manual should use a hard-coded or empty date. Thoughts? Kristaps -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv