Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Sat, 22 Sep 2001 10:00:44 +0100
Message-ID: <6396-Sat22Sep2001100045+0100-starksb@ebi.ac.uk>
X-Mailer: 21.5  (beta2) "artichoke" XEmacs Lucid (via feedmail 9-beta-7 I);
	VM 6.92 under 21.5  (beta2) "artichoke" XEmacs Lucid
From: David Starks-Browning <starksb@ebi.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Edmund Horner <ejrh@paradise.net.nz>
Cc: <cygwin@cygwin.com>
Subject: RE: Periodic plea for someone to work on cygwin docs
In-Reply-To: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F1B1@itdomain002.itdomain.net.au>
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F1B1@itdomain002.itdomain.net.au>

Edmund,

I can help you with cvs.  I just setup FAQ maintenance on a new
machine so it's fresh in my memory.  We would share a Makefile in
winsup/doc and this may need work, and I'm willing to help with
that.

Cheers,
David

On Saturday 22 Sep 01, Robert Collins writes:
> > -----Original Message-----
> > From: Christopher Faylor [mailto:cgf@redhat.com]
> 
> > I'd rather not have to provide active guidance about CVS 
> > usage and I can't
> > provide any guidance at all about sgml.  Having looked at Cygwin's use
> > of sgml, I can say that it seems pretty intuitive, though.
> 
> I'm not able to spend time on the doco, but I do know docbook - which is
> the SGML DTD the cygwin doco is written in. I'm happy to provide
> guidance if and when it's needed.
> 
> Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

