From: Paul Stodghill <stodghil@cs.cornell.edu>
Subject: Re: Patch for filesystems that do not support chmod.
Date: Thu, 20 May 2004 13:08:41 -0400 [thread overview]
Message-ID: <r99smdvc9gm.fsf@barney-xp.cs.cornell.edu> (raw)
In-Reply-To: <m3y8nnnbwu.fsf@defun.localdomain> (Jesper Harder's message of "Thu, 20 May 2004 03:08:01 +0200")
> If XEmacs+cygwin is the odd man out, I think it would be better to
> make it consistant with the other ports.
XEmacs will raise an exception on any platform when the call to chmod
fails. This can happen, for instance, if you do not own the file being
chmod'ed. I believe that this can also happen for certain file modes on
SMB file systems. Someone with a Linux system and a Samba mounted file
system could verify this.
This is not a platform bug. IMO, Gnus should not request a file mode
that the underlying filesystem cannot support.
next prev parent reply other threads:[~2004-05-20 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 12:53 Paul Stodghill
2004-05-19 13:26 ` Jesper Harder
2004-05-19 23:39 ` Lars Magne Ingebrigtsen
2004-05-20 1:08 ` Jesper Harder
2004-05-20 16:43 ` Lars Magne Ingebrigtsen
2004-05-20 17:08 ` Paul Stodghill [this message]
2004-05-20 17:28 ` Paul Stodghill
2004-05-20 23:40 ` Jon Ericson
2004-05-22 23:29 ` Lars Magne Ingebrigtsen
2004-05-20 19:58 ` Jesper Harder
2004-05-20 17:04 ` Paul Stodghill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=r99smdvc9gm.fsf@barney-xp.cs.cornell.edu \
--to=stodghil@cs.cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).