Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 6 Oct 2004 13:18:24 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Reini Urban <rurban AT x-ray DOT at>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Known Issues: document missing POSIX compliance and other unexpected behaviour
In-Reply-To:	<41641A0E.4030803@x-ray.at>
Message-ID:	<Pine.GSO.4.61.0410061316030.24166@slinky.cs.nyu.edu>
References:	<41640B07 DOT 2040607 AT x-ray DOT at> <20041006153205 DOT GH29289 AT trixie DOT casa DOT cgf DOT cx> <41641A0E DOT 4030803 AT x-ray DOT at>
MIME-Version:	1.0
X-Scanned-By:	MIMEDefang 2.39

On Wed, 6 Oct 2004, Reini Urban wrote:

> Christopher Faylor schrieb:
> > On Wed, Oct 06, 2004 at 05:11:03PM +0200, Reini Urban wrote:
> > > I found no document where missing POSIX functionality is listed
> > > and where other non-POSIX but expected typical UNIX functionality and/or
> > > behaviour are different or missing. The user guide is a bit short on that.
> >
> > The only way such a document would be useful would be if it was
> > rigorously maintained.
>
> ok.
>
> > You show the reason why below when you quote out-of-date parts of the
> > existing documentation.
> > It is certainly worthwhile to sweep through the docs and get everything
> > up-to-date, though.
> >
> >[snip]
> > I think I'll stop here.  You're showing that it would be worthwhile to
> > go through the document and look for stuff that is out of date.
> >
> > I guess that would be a job for Corinna, Pierre, and me, since
> > no one else seems to understand these issues.  If someone else wants
> > to take a stab at it, however, please feel free.
>
> Sure, but where?
> In the list or elsewhere? As I suggested in a wiki for some while until
> it is in the docs. Seems to work out good, even if it should be
> "rigorously maintained", as you said.

Volunteer to become a (rigorous) maintainer of these docs sections.  Send
patches to the cygwin list.  After a while, you may get commit privileges
so you can commit your own docs patches.
<http://cygwin.com/acronyms/#SHTDI>.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -