Re: cvs commit: src/usr.bin/calendar calendar.1

[ Available lists | Index of cvs-all | Month of Oct 2001 | Week of 1 Oct 2001 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Ruslan Ermilov <ru@FreeBSD.org>
Date
1 Oct 2001 02:05:30
Subject
Re: cvs commit: src/usr.bin/calendar calendar.1
Message-ID
20011001120308.B7304@sunbay.com


[ Hide this part ]
On Mon, Oct 01, 2001 at 06:27:29PM +0930, Greg Lehey wrote:
> On Monday, 1 October 2001 at 11:41:53 +0300, Ruslan Ermilov wrote:
> > On Mon, Oct 01, 2001 at 06:04:43PM +0930, Greg Lehey wrote:
> >> On Monday, 1 October 2001 at 11:29:16 +0300, Ruslan Ermilov wrote:
> >>> On Mon, Oct 01, 2001 at 05:47:10PM +0930, Greg Lehey wrote:
> >>>> On Monday, 1 October 2001 at 10:08:57 +0300, Ruslan Ermilov wrote:
> >>>>> On Sun, Sep 30, 2001 at 07:35:52PM -0700, Greg Lehey wrote:
> >>>>>> grog 2001/09/30 19:35:52 PDT
> >>>>>>
> >>>>>> Modified files:
> >>>>>> usr.bin/calendar calendar.1
> >>>>>> Log:
> >>>>>> Add description for calendar.freebsd.
> >>>>>>
> >>>>>> Revision Changes Path
> >>>>>> 1.23 +3 -1 src/usr.bin/calendar/calendar.1
> >>>>>
> >>>>> FreeBSD is to be spelled ".Fx" in mdoc(7).
> >>>>
> >>>> That doesn't work on other systems, and even on FreeBSD it only tends
> >>>> to obfuscate.
> >>>
> >>> This works on other systems that use the compatible version of
> >>> the mdoc(7) macro package distributed with Groff.
> >>
> >> Precisely. What's the advantage?
> >>
> > .Fx uses a special font/size and prevents undesirable hyphenation.
> > When used with the version argument, it also checks the version.
>
> I suppose that's a reason.
>
> >>>>> Also, you forgot to update document date.
> >>>>
> >>>> My understanding was that the document date had nothing to do with
> >>>> when it was updated. Can you state the policy?
> >>>>
> >>> This is from share/examples/mdoc:
> >>>
> >>> .\" Note: The date here should be updated whenever a non-trivial
> >>> .\" change is made to the manual page.
> >>
> >> This change was trivial.
> >>
> > I myself consider the following changes trivial: markup and/or spelling
> > fixes. If you change the content, OTOH, e.g. you document new option or
> > new functionality, or add a paragpraph about functionality that wasn't
> > previously documented, you should bump document date.
> >
> > Note "should" but not "must". This is because if you don't do this,
> > I will. :-)
>
> No, that is contrary to the committer guidelines. Please don't do
> that.
>
> I am getting thoroughly fed up with your attitude. You have no
> authority to dictate this sort of change. Sure, you've done a lot of
> good grunt-work tidying up the man pages, but things would have been a
> lot easier to handle if you didn't try to impose such a policeman-like
> attitude, and discussed things instead. What you personally consider
> to be trivial is of no consequence. We have a docmeister who doesn't
> try to throw his weight around, and who hasn't commented on most of
> these trivialities.
>
Note that I replied in private, you turned this into public. Well, your
right. So far, you are the only person who doesn't agree on almost every
bit of mdoc(7) fixes I made. Also, if you don't know, I am the official
mdoc(7) maintainer in FreeBSD. This is documented in the Committer's
Guide, and was committed by docmeister (that's how you call Nik I suppose).

> Personally, I would much rather see the date changed every time the
> document was changed. That would alert people to the fact that
> *something* has changed.
>
Markup and spelling don't qualify. Everything else -- yes.


Cheers,
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine

http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message



Elapsed time: 0.145 seconds