Today, Steven A. DuChene wrote forth saying... > On Thu, Sep 19, 2002 at 01:23:49PM -0700, matt massie wrote: > > Today, Steven A. DuChene wrote forth saying... > > > > > It does answer the question but shouldn't the monitor-docs files include > > > some details of what the various options do/mean/syntax of stuff that > > > can go in that file? > > > > so you think that explanations of each option is too sparse? each option > > is listed in the example with a short explanation (too short?) and the > > default value. > > > > No, appearently if the monitor-core stuff isn't found when building the > monitor-docs stuff there are NO details included in the resulting html > stuff. I'd say that was a little sparse. :-)
hehe... so now i understand. it looks like i need to create a README.CVSusers for the documentation to warn of this. i would recommend though that you just download the docs from the documentation web page (unless of course you want to edit the docs (or merge them) for your oscar group then you'll need CVS). -matt
