Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <03b901c20a85$75cb2190$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: "Earnie Boyd" <Cygwin-Developers AT cygwin DOT com>
Cc: <cygwin-developers AT cygwin DOT com>
References: <026901c20a46$245b0ad0$6132bc3e AT BABEL> <20020602163324 DOT GB12502 AT redhat DOT com> <038001c20a7d$2fea7700$6132bc3e AT BABEL> <3CFA941F DOT 9C5C35D7 AT yahoo DOT com>
Subject: Re: stat(2) wierdness
Date: Sun, 2 Jun 2002 23:33:03 +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

"Earnie Boyd" <earnie_boyd AT yahoo DOT com> wrote:
> I thought that your post met the "Discussions of upcoming net releases
> are also appropriate" rule but I must have been wrong.  Perhaps stronger
> attention to "Heads up before net release" or a different subject would
> have made the post clearer as to your intent.  Suggesting that you're
> looking for the bug to squash may have also helped.

That was much my thinking really: Chris had said that a new release was on
its way and so people should flag up problems with it. And in this
particular case I wasn't about to try and fix it since I knew Chris was
already working in that area.

Then again, the original "The road to 1.3.11 -- please try the latest
snapshot" message was posted in the *cygwin* mailing list and not here, so I
should have stayed there.

This all feels like I'm trying to justify myself so I should stop but then
again I suppose I felt a bit miffed by Chris's original reply. Perhaps if it
had read "Thanks for the bug report but . . ." rather than just containing
that (gentle) reprimand.

Ah well, I see the bug's fixed so all's well that ends well.

Best to all,

// Conrad