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: Fri, 14 Sep 2001 12:18:21 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: how-xxx-works.txt
Message-ID: <20010914121821.A2365@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.21i

If you've been following the cygwin-cvs mailing list you've probably
noticed that I"ve been checking how-xxx-works.txt files into the cygwin
repository.  They represent my understanding of how certain "arcane"
elements of cygwin operate.

I started writing a (currently incomplete) how-signals-work.txt file at
Corinna's request and I thought it would probably be a good idea to add
a few more, too.  I just updated the how-cygheap-works.txt file to
reflect the changes that I made last night.

These are all works in progress and may not be much better than nothing
but, at least they clarify my understanding of what's going on.  :-)

cgf