http://cygwin.com/acronyms/#TOFU
On Jan 25 11:25, brassrat wrote:
>
> I agree that the having an R/O attribute conflicts with the concept of ACLS;
> however, it is not true that the chmod command does not change this flag.
> For example,
> if you chmod +w a file with the R/O flag 'set' the R/O
I agree that the having an R/O attribute conflicts with the concept of ACLS;
however, it is not true that the chmod command does not change this flag.
For example,
if you chmod +w a file with the R/O flag 'set' the R/O flag is reset.
(maybe this is a side-effect of the ACL-based processing withi
On Jan 25 07:55, brassrat wrote:
>
> The source control package i use at work is sensitive to the 'read-only'
> attribute of Windows files.
> prior to 1.7, the command 'chmod -w DIR/FILE' worked fine.
> now, with 1.7, chmod -w FILE no longer sets the read-only attribute - i
> guess because
> fort
3 matches
Mail list logo
