Date: Wed, 20 Mar 2002 11:40:13 -0600 From: Mike Meyer <mwm-dated-1017078014.aba542@mired.org> To: darklogik@pittgoth.com Cc: swear@blarg.net, freebsd-doc@FreeBSD.ORG Subject: Re: docs/36042: [PATCH] There's not a good description of shared builds in the handbook Message-ID: <15512.51581.789216.308497@guru.mired.org> In-Reply-To: <3C98C11E.30902@pittgoth.com> References: <200203192120.g2JLK3o17280@freefall.freebsd.org> <mfr8mf98vb.8mf@localhost.localdomain> <15512.3992.905972.279159@guru.mired.org> <20020320000727.284a00c1.darklogik@pittgoth.com> <15512.44867.930654.886921@guru.mired.org> <3C98C11E.30902@pittgoth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In <3C98C11E.30902@pittgoth.com>, Tom Rhodes <darklogik@pittgoth.com> typed: > Mike Meyer wrote: > > In <20020320000727.284a00c1.darklogik@pittgoth.com>, Tom Rhodes <darklogik@pittgoth.com> typed: > I'm not going to get myself into this arguement, if you want to argue > using rfc standards, then please notice how the rfc's have two spaces > after each sentance as observed on faq.org/rfcs ;) Uh huh. > It is also a tad bit easier for translaters... If you really want to > propose a large arguement, then just look at it like this, in the doc > project we use two spaces as a set standard for the documents we > produce. We have followed this for awhile now, if we let everyone > submit under any standard, we would have some ugly looking documentation. The doc project accepts text that isn't even marked up. If the doc project committers can mark up text, I think they can "fix" text that doesn't adhere to what the author thinks is an antiquated standard. If they can't, they can close the PR, and leave this activity undocumented until someone comes along who'll leap through all the doc project hurdles to write it up. If it is closed without being used, I will then consider whether or not I want to publish this on my own site. I loathe that kind of thing, because that doesn't get the document reviewed or maintained by the doc project, to the detriment of both the document and the FreeBSD project. I probably won't, but will simply refer people to the PR until it is obsolete. But I certainly won't be writing any more FAQ or handbook entries. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15512.51581.789216.308497>