From owner-freebsd-questions Wed Sep 16 16:50:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12058 for freebsd-questions-outgoing; Wed, 16 Sep 1998 16:50:26 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11885 for ; Wed, 16 Sep 1998 16:49:24 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA27122; Wed, 16 Sep 1998 16:48:56 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 16 Sep 1998 16:48:56 -0700 (PDT) From: Doug White To: Gildas Perrot cc: FAQ@FreeBSD.ORG Subject: Re: It would be great to mark FAQ modifications in it In-Reply-To: <199809161443.QAA10457@epiphore.francenet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Sep 1998, Gildas Perrot wrote: > Hi, > > I think it would be great to mark FAQ modifications in it as it is done in > http://www.cs.ruu.nl/wais/html/na-dir/comp-sys-sun-faq.html : > > "This article includes answers to the following questions, which are loosely > grouped into categories. Questions marked with a '+' indicate questions > new to this issue; those with significant changes of content since the > last issue are marked by '!'." Yuck. :( that's a lot of maintenance between revisions. To boot the FAQ is generated from SGML sources every 12 hours or so, so the concept of 'issue' doesn't really apply. The CVS tree handles it anyway. if you want to see the changes to the FAQ, see http://www.freebsd.org/cgi/cvsweb.cgi/doc/FAQ/. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message