From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: romain@orebokech.com, emacs-devel@gnu.org, eggert@cs.ucla.edu
Subject: Re: set-file-extended-attributes and backups
Date: Mon, 24 Dec 2012 05:44:40 +0200 [thread overview]
Message-ID: <8338ywp107.fsf@gnu.org> (raw)
In-Reply-To: <jwva9t4gtc2.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Romain Francoise <romain@orebokech.com>, eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Sun, 23 Dec 2012 19:59:35 -0500
>
> > How about changing its return value instead? Say, return t if ACLs
> > set, nil otherwise. It always bothers me to have an API that silently
> > fails without any tangible indication.
>
> I think it should fail (i.e. signal an error) for any case where the
> file's ACLs were not set as requested.
ENOTSUP usually means the filesystem doesn't support ACLs. Having an
error that every single use of it will want to ignore doesn't seem to
be useful.
next prev parent reply other threads:[~2012-12-24 3:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 14:53 set-file-extended-attributes and backups Eli Zaretskii
2012-12-21 16:00 ` Paul Eggert
2012-12-21 16:44 ` Eli Zaretskii
2012-12-21 17:48 ` Paul Eggert
2012-12-21 18:08 ` Eli Zaretskii
2012-12-21 18:31 ` Paul Eggert
2012-12-23 16:59 ` Romain Francoise
2012-12-23 17:35 ` Eli Zaretskii
2012-12-24 0:59 ` Stefan Monnier
2012-12-24 3:44 ` Eli Zaretskii [this message]
2012-12-24 5:18 ` Stefan Monnier
2012-12-24 8:25 ` Michael Albinus
2012-12-24 16:24 ` Eli Zaretskii
2012-12-21 18:31 ` Romain Francoise
2012-12-22 23:03 ` Fabrice Popineau
2012-12-23 3:54 ` Eli Zaretskii
2012-12-23 17:17 ` Eli Zaretskii
2012-12-22 16:05 ` Stefan Monnier
2012-12-22 17:03 ` Eli Zaretskii
2012-12-23 13:37 ` Stefan Monnier
2012-12-29 17:20 ` Eli Zaretskii
2012-12-29 17:50 ` Eli Zaretskii
2012-12-29 19:12 ` Michael Albinus
2012-12-30 10:59 ` Michael Albinus
2012-12-30 17:21 ` 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=8338ywp107.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=romain@orebokech.com \
/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).