Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <038001c20a7d$2fea7700$6132bc3e@BABEL> From: "Conrad Scott" To: References: <026901c20a46$245b0ad0$6132bc3e AT BABEL> <20020602163324 DOT GB12502 AT redhat DOT com> Subject: Re: stat(2) wierdness Date: Sun, 2 Jun 2002 22:33:50 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Christopher Faylor" wrote: > I guess it's time for my periodic "this is not a bug reporting mailing > list" observation. > > If you are going to post here, there is an assumption that you have done > more than just notice a bug. It's called "cygwin-developers" becuase > the hope is that you will track down the problem more thoroughly than a > normal cygwin mailing list message. > > Bug reports are fine in the cygwin mailing list. The bar is a little higher > here. My apologies: I hadn't realised that there was quite such a restrictive notion of posting in this group. It seemed appropriate to post here since the bug report applied to an unreleased (therefore, a developer only?) version. I'm just learning the ropes here: I'll try to be a good boy in future. // Conrad