Date: Fri, 12 Sep 2003 16:11:26 +0200 From: Josef El-Rayes <j.el-rayes@daemon.li> To: Ceri Davies <setantae@submonkey.net>, "Simon L. Nielsen" <simon@FreeBSD.org>, Christian Brueffer <chris@unixpages.org>, freebsd-doc@FreeBSD.org Subject: Re: docs/56729: [patch] artciles/pr-guidelines: explain meaning of MFC Message-ID: <20030912141126.GC1068@daemon.li> In-Reply-To: <20030912111813.GA75659@submonkey.net> References: <200309120920.h8C9KGZ8091585@freefall.freebsd.org> <20030912093107.GH635@unixpages.org> <20030912093846.GK76802@submonkey.net> <20030912103331.GA388@FreeBSD.org> <20030912111813.GA75659@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ceri Davies <setantae@submonkey.net> wrote: > Yeah, those are the lines I was thinking along. > My reference to "relevant elements" was that there are very likely <glossary> > elements or similar already, which we can make use of. i wanted to start collecting some terms for glossary as some questions arose: i am wondering on how to realize this. should it be more of an index, with a crosslink to the place where it gets explained or like this: MFC: ...merge from current, action... <a href="..">read handbook..</a> with a short explanation and a link when there is a place where it gets explainend more detailed. should there be a certain "treshhold" like, only use freebsd specific terms or not trivial terms or should we include every term like "unix, ports, packages..."? -josef -- www: http://www.daemon.li nic-hdl: JER1080312-NICAT BSD in AT: www.bsdcode.at "Make World - Not War!"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030912141126.GC1068>