Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Thu, 7 Dec 2000 12:30:20 -0500
Message-Id:	<200012071730.MAA04970@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	tailbert AT yahoo DOT com
CC:	cygwin-developers AT sources DOT redhat DOT com
In-reply-to:	<FMEOJCMLNIMPBKAPFPIHCEFHCFAA.tailbert@yahoo.com>
Subject:	Re: winsup/doc layout change?
References:	<FMEOJCMLNIMPBKAPFPIHCEFHCFAA DOT tailbert AT yahoo DOT com>

> 	cygwin-api/
> 	cygwin-api-int/
> 	cygwin-ug/
> 	cygwin-ug-net/

The *-net variants are derived from the base variant.  There shouldn't
be any need to keep the two separate, and jade puts the output files
in separate subdirectories anyway.

> 	doctool/		<- source for doctool.exe

A whole directory for one source file?

> 	sgml/			<- sgml sources
> 	texinfo/		<- texinfo sources

Sources for what?  If they're part of the api, ug, or faq docs then
they'd already be elsewhere.

> 	text/			<- random text files until we have real docs

Those could just stay in the doc/ directory.

> 	utils/		<- sgml files for the apps in utils

I'd rather keep those with the utils.  DJGPP history has shown that
keeping doc files adjacent to source files promotes doc writing.  The
whole point of doctool is to put the documentation *in* the sources,
to push this concept even further.

- Raw text -