Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID:	<00e801c140fc$74b6ae30$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
References:	<20010917183734 DOT D10081 AT cygbert DOT vinschen DOT de> <20010918103321 DOT B1332 AT dothill DOT com> <20010918113523 DOT B510 AT redhat DOT com>
Subject:	Re: WriteFile() whacks st_atime patch
Date:	Wed, 19 Sep 2001 21:15:56 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	19 Sep 2001 11:24:13.0090 (UTC) FILETIME=[9BFAE820:01C140FD]

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
I actually proposed the link option since it fixes the problem at the
> source.  If you link mutt with setftime.o you will not be constantly
> saying "Didn't you read the FAQ, you idiot?  You have to set
> CYGWIN=ftime!" mutt will just work.
>
> The issue of mutt not working correctly has been a hot mailing list
> topic.  However, I don't think that the issue of atime not being set
the
> same way UNIX sets it has really been of generic enough interest to
> warrant YA CYGWIN variable.

I concur, but with slightly different reasoning.

The overhead of the fix will seriously impact anything trying performing
lots of writes, whether or not it cares about atime. I.e. a newsspool or
squid. Installing mutt shouldn't be a cause to cripple all the other
software on the system.

So _any_ solution needs to be specific, or low overhead. Mutt and
related packages can have makefile changes propogated upstream, or at a
minimum they will be in the source package here, and anyone porting new
software across that interacts with the files mutt cares about *will
have trouble anyway*. ((binmode|automode|textmode).o | setmode()) at a
minimum.

Rob

- Raw text -