Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: cygwin stat code (again)
- X-seq: zsh-workers 14491
- From: cgf@xxxxxxxxxx (Christopher Faylor)
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: cygwin stat code (again)
- Date: Sat, 26 May 2001 17:37:58 GMT
- Cache-post-path: ohreally.bosbc.com!unknown@xxxxxxxxxxxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Organization: Cygnus Solutions
- References: <000201c0daa5$0126c170$21c9ca95@xxxxxxxxxxxxxx> <000201c0daa5$0126c170$21c9ca95@xxxxxxxxxxxxxx> <1010512104101.ZM6168@xxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: cgf@xxxxxxxxx
- Sender: cgf@xxxxxxxxx
In article <1010512104101.ZM6168@xxxxxxxxxxxxxxxxxxxxxxx>,
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>On May 12, 9:32am, Andrej Borsenkow wrote:
>} Subject: RE: PATCH: cygwin stat code (again)
>}
>} > mflags in stat under cygwin shouldn't be const, since it needs to be
>} > initialised at run time.
>}
>} Was not this already fixed?
>
>PWS made a different change; his patch made
>
> static const mode_t mflags[9]
>
>into
>
> static mode_t mflags[9]
>
>whereas my patch changed the values within the array. I should have
>caught that the `const' needed to go away too.
FWIW, I've been convinced that this change to Cygwin caused many more
problems than it solved so it has been reverted in 1.3.2.
FYI,
cgf
Messages sorted by:
Reverse Date,
Date,
Thread,
Author