Yes. Yes, yes/yes.
I had been naively assuming that the structure of the full TOC
would make it obvious what each file is actually for.
> -----Original Message-----
> From: Tom Walsh [mailto:firstname.lastname@example.org]
> Sent: Thursday, March 22, 2001 12:33 PM
> To: ucsimm@uClinux.com
> Subject: Re: AW: [uCsimm] Example Code
> Alex Perry wrote:
> > appends it to the relevant file. Then, do a nightly build of the
> > document to be PS, PDF and browsable HTML. The latter has a link
> > to the page that explains how to add paragraphs to the document.
> > The document can then grow like a FAQ, except that (at some point)
> > people will start taking the sections and editing for continuity.
> Kind of like a knowledge base? But more organized than a
> collection of
> semi-related articles, start out with a framework, then let
> people add /
> edit portions of the "tree" and describe (aka document) what the
> various files are there for?
> Tom Walsh - WN3L - Embedded Systems Consultant
> 'www.openhardware.net', 'www.cyberiansoftware.com'
> "Windows? No thanks, I have work to do..."
> This message resent by the email@example.com list server
This message resent by the firstname.lastname@example.org list server http://www.uClinux.com/
This archive was generated by hypermail 2b30 : Sun Apr 07 2002 - 00:01:42 EST