From: Josh <josh@foxtail.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Валерия Лихушина" <ran@lasgalen.net>,
16133@debbugs.gnu.org, "Paul Eggert" <eggert@cs.ucla.edu>
Subject: bug#16133: 24.3; copy-file fails on chmod when copying to FAT filesystem
Date: Sat, 14 Dec 2013 13:21:58 -0800 [thread overview]
Message-ID: <CANdFEAH-D4mk7SyMcjFojhYfBAkfwz89A0_qep7=yyvK5sd2NA@mail.gmail.com> (raw)
In-Reply-To: <837gb7f8vm.fsf@gnu.org>
On Sat, Dec 14, 2013 at 12:57 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Josh <josh@foxtail.org>
>> Date: Sat, 14 Dec 2013 12:46:59 -0800
>> Cc: Paul Eggert <eggert@cs.ucla.edu>, Artem Chuprina <ran@lasgalen.net>,
>> 16133@debbugs.gnu.org
>>
>> On Sat, Dec 14, 2013 at 12:19 PM, Glenn Morris <rgm@gnu.org> wrote:
>> > I don't know how we tidy this up for the future though.
>> > Add yet another optional argument "error-if-permissions-fail"? Yuck.
>>
>> It might be reasonable to error only when the existing
>> PRESERVE-UID-GID argument was non-nil.
>
> That argument has nothing to do with mode bits, which is what this bug
> is about.
That argument being nil indicates that the user doesn't care about
preserving UID and GID. Are there cases when the user would care
about preserving mode bits but not UID and GID?
next prev parent reply other threads:[~2013-12-14 21:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 19:51 bug#16133: 24.3; copy-file fails on chmod when copying to FAT filesystem Artem Chuprina
2013-12-13 22:51 ` Glenn Morris
2013-12-13 22:55 ` Glenn Morris
2013-12-14 10:10 ` Artem Chuprina
2013-12-14 20:19 ` Glenn Morris
2013-12-14 20:46 ` Josh
2013-12-14 20:57 ` Eli Zaretskii
2013-12-14 21:21 ` Josh [this message]
2013-12-15 3:44 ` Eli Zaretskii
2013-12-14 20:55 ` Eli Zaretskii
2013-12-14 21:07 ` Achim Gratz
2013-12-15 14:38 ` Artem Chuprina
2013-12-16 14:15 ` Stefan Monnier
2013-12-20 23:27 ` Paul Eggert
2013-12-22 0:01 ` Paul Eggert
2013-12-22 3:47 ` Eli Zaretskii
2013-12-22 4:01 ` Paul Eggert
2013-12-22 15:50 ` Artem Chuprina
2013-12-22 19:03 ` Paul Eggert
2013-12-22 20:13 ` Artem Chuprina
2013-12-23 23:58 ` Paul Eggert
2013-12-24 6:52 ` Artem Chuprina
2013-12-24 9:58 ` Andreas Schwab
2013-12-24 10:22 ` Artem Chuprina
2013-12-24 17:39 ` Paul Eggert
2013-12-24 16:51 ` Artem Chuprina
2013-12-29 18:31 ` Paul Eggert
2013-12-22 16:24 ` Eli Zaretskii
2013-12-22 17:37 ` Paul Eggert
2013-12-22 18:35 ` Eli Zaretskii
2013-12-22 18:54 ` Paul Eggert
2013-12-22 20:32 ` Artem Chuprina
2013-12-22 21:00 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANdFEAH-D4mk7SyMcjFojhYfBAkfwz89A0_qep7=yyvK5sd2NA@mail.gmail.com' \
--to=josh@foxtail.org \
--cc=16133@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=ran@lasgalen.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).