unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Romain Francoise <romain@orebokech.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH v2] POSIX ACL support
Date: Thu, 06 Dec 2012 20:45:46 +0100	[thread overview]
Message-ID: <87zk1rm0b9.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <83boe9r1lw.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 04 Dec 2012 22:42:03 +0200")

Hi Eli,

Eli Zaretskii <eliz@gnu.org> writes:

> Suggest an additional entry "@cindex access control list" here.

Ok.

> We don't mention "ACL" or explain it anywhere else in the manual.  So
> this acronym should be explained here, and its first use should use
> @dfn, as we do with any new terminology.

Makes sense. I'll try to come up with a description general enough to
apply to all potential platforms.

>> +DEFUN ("file-acl", Ffile_acl, Sfile_acl, 1, 1, 0,
>> +       doc: /* Return ACL entries of file named FILENAME, as a string.
>> +Return nil if file does not exist or is not accessible, or if Emacs was
>> +not compiled with ACL support.  */)

> The last sentence of the doc string is inaccurate, because remote
> files are supported even if Emacs was not built with ACL support.

Yes... if there's an implementation of file-acl for the remote handler.
This bit was inherited from the SELinux functions, which have a similar
docstring. I'm not sure how to phrase it better, though.

Thanks!



  reply	other threads:[~2012-12-06 19:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02 20:04 [PATCH v2] POSIX ACL support Romain Francoise
2012-12-04 20:42 ` Eli Zaretskii
2012-12-06 19:45   ` Romain Francoise [this message]
2012-12-07  8:19     ` Michael Albinus
2012-12-07  9:32       ` Eli Zaretskii
2012-12-05  2:28 ` Glenn Morris
2012-12-05  3:53   ` Eli Zaretskii
2012-12-05  4:09     ` Glenn Morris
2012-12-05 16:16       ` Eli Zaretskii
2012-12-05 17:18         ` Glenn Morris
2012-12-06 19:48   ` Romain Francoise
2012-12-06 21:33     ` Stefan Monnier

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=87zk1rm0b9.fsf@silenus.orebokech.com \
    --to=romain@orebokech.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).