| www.delorie.com/archives/browse.cgi | search |
On Wed, Sep 19, 2001 at 09:15:56PM +1000, Robert Collins wrote: >----- 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. Right. It is easy to set a CYGWIN environment variable without fully understanding the implications. I could easily see someone setting CYGWIN=ftime and then being disgusted with Cygwin's I/O throughput. cgf
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |