Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Tue, 9 Nov 1999 15:23:22 -0500
Message-Id: <199911092023.PAA30829@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: dwyatt AT sunflower DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <199911091904.OAA15801@dagda.sunflower.com>
	(dwyatt AT sunflower DOT com)
Subject: Re: Building cygwin32_ipc-1.03 for v1.0 - questions about v1
References:  <199911091904 DOT OAA15801 AT dagda DOT sunflower DOT com>


> Why is the v1 release so divergent from b20.1 development -

Because b20.1 is old.  The CDROM (and the snapshots) include much
newer sources, and the changes were deemed (at the time) to be worth
the annoyance of changing.  When we release the next beta, it should
be compatible with the CD (or newer, of course).

> Oh, and one other thing - why no man2 entries?

Time and effort.  The documentation was already available in the
formats we shipped it in.  We would have had to have written a
converter if we wanted man pages instead.  Yes, I miss them too.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com