Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Dec 1999 16:16:41 +0100
From:      Jeroen Ruigrok van der Werven <asmodai@bart.nl>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        doc@FreeBSD.org, Poul-Henning Kamp <phk@FreeBSD.org>
Subject:   Re: "ze" and "zp" drivers removed...
Message-ID:  <19991210161641.G85568@lucifer.bart.nl>
In-Reply-To: <199912101504.KAA46818@server.baldwin.cx>; from jhb@FreeBSD.org on Fri, Dec 10, 1999 at 10:04:44AM -0500
References:  <19991210150908.D85568@lucifer.bart.nl> <199912101504.KAA46818@server.baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
-On [19991210 16:10], John Baldwin (jhb@FreeBSD.org) wrote:
>
>On 10-Dec-99 Jeroen Ruigrok van der Werven wrote:
>> -On [19991210 14:00], Jeroen Ruigrok van der Werven (asmodai@bart.nl) wrote:
>>>-On [19991210 12:00], Poul-Henning Kamp (phk@FreeBSD.ORG) wrote:
>>>>
>>>>I don't know if there are any refererences to the ze and zp drivers
>>>>in the handbook which should be removed.
>>>
>>>Found a patch attached.
>> 
>> I can't spell jack lately.
>> 
>> And I removed a bit too much.
>> 
>> Find a new patch attached.
>
>Ok, the problem with this patch is that we can't just remove the references
>entirely because the drivers still exist in 3.x.  In fact, looking over this
>chapter, it is still very much 2.2.x specific.  Do we have the osversionmin,
>osersionmax, and other variables awailable, as well as the support for them in
>the toolset so that we can start marking some parts of the documentation as
>specific to certain releases?  It's either that or branch -doc, IMHO.

I know.  My patch was more of the Danish type. =)

Last time I talked this over with Nik we came to some sort of id="" like
argument to a tag which would be os="".

But I am now starting to think a branching of the handbook to the
relevant versions might be desirable.  This lessens the clutter we get
from putting too much in the same document.

OTOH, after remembering something about os="" arguments.  We have one
document for say kernel configuration which, when given proper make
arguments, will generate relevant documentation for a given release.  We
could then tag this along with a release or something along that order.

-- 
Jeroen Ruigrok van der Werven          Network- and systemadministrator
<asmodai@bart.nl>                      bART Internet Services /
Tel: +31 - (0) 10 - 240 39 70          VIA NET.WORKS Netherlands


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?19991210161641.G85568>