Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 14 Jun 2002 12:26:04 +0100 Message-ID: <4945-Fri14Jun2002122604+0100-starksb@ebi.ac.uk> From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nicholas Wourms Cc: cygwin@cygwin.com Subject: Re: pthread In-Reply-To: <20020613182640.9467.qmail@web21003.mail.yahoo.com> References: <20020613153442.GA24314@redhat.com> <20020613182640.9467.qmail@web21003.mail.yahoo.com> On Thursday 13 Jun 02, Nicholas Wourms writes: > > --- Christopher Faylor wrote: > > On Thu, Jun 13, 2002 at 08:35:26PM +1000, Robert Collins wrote: > > >The doco is outdated, all those functions are implemented. > > > > Anyone interested in updating the documentation? > > > > At the very least we should remove the "unimplemented" tags. > > Do patches against htdocs belong here or in cygwin-patches? What documentation are you talking about? The "User's Guide", "API Reference" or FAQ? In each case, one updates the source in winsup/doc (sgml for ug and api, texinfo for the faq), and generates the contents of htdocs from that. For these, you don't patch htdocs directly. I see the FAQ needs updating w.r.t. these calls, and I've already got a backlog of FAQ updates to apply, so I'll see what I can do about it this weekend. I can't do it during the workday, unfortunately. Regards, David -- 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/