From owner-freebsd-hackers Fri Dec 12 14:35:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01213 for hackers-outgoing; Fri, 12 Dec 1997 14:35:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01196 for ; Fri, 12 Dec 1997 14:34:58 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id OAA19833; Fri, 12 Dec 1997 14:15:39 -0800 (PST) Message-ID: <19971212141538.57181@micron.mini.net> Date: Fri, 12 Dec 1997 14:15:38 -0800 From: Jonathan Mini To: Adam Turoff Cc: "'jkh@time.cdrom.com'" , "'j_mini@efn.org'" , "'freebsd-hackers@FreeBSD.ORG'" Subject: Re: Kernel Config datafile... Reply-To: Jonathan Mini References: <34918F3E@smginc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <34918F3E@smginc.com>; from Adam Turoff on Fri, Dec 12, 1997 at 11:22:00AM -0800 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hmmm. No flames about SGML (read below), but I will yell azt you for using a mailer that doesn't generate In-Reply-To headers. These headers allow mailers like mutt to keep all incoming messages sotrted by threads, and without them the threads get all mixed up. Most mailers generate them, except for a few. PLEASE PLEASE PLEASE upgrade to a mailer that will generate In-Reply-To headers. Adam Turoff stands accused of saying: > > I don't want to start a flame war here, but I've heard the > topic of a configuration file that needed to be both > ASCII and vi/emacs editable as well as store relational > data as well. > > Allow me to spread the evangelism a wee tad and mention > SGML/XML. This would give the advantage of encoding > multiple aspects of the kernel config data in a single > ASCII (technically, Unicode) file. I was thinking about using SGML actually, but I hadn't got that far. We'll see about whether or not it turns out to be the easiest format to deal with. I think it might. For example : You get the idea. We'll see. -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five."