From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: romain@orebokech.com, michael.albinus@gmx.de, 13226@debbugs.gnu.org
Subject: bug#13226: 24.3.50; set-file-acl on MS Windows shall check ACL string format
Date: Sat, 22 Dec 2012 16:19:47 +0200 [thread overview]
Message-ID: <83y5gqp3ss.fsf@gnu.org> (raw)
In-Reply-To: <jwvtxrhsfxt.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: michael.albinus@gmx.de, romain@orebokech.com, 13226@debbugs.gnu.org
> Date: Wed, 19 Dec 2012 19:53:08 -0500
>
> > Currently, it could be either a string or nil. The latter means "no
> > ACL". Do you want to undocument both of these possibilities? It
> > sounds too radical to me.
>
> Of course nil is perfectly fine, but the string one shouldn't
> be documented (and ideally, the it shouldn't be a string but an opaque
> object).
Done (the documentation part) in trunk revision 111296.
next prev parent reply other threads:[~2012-12-22 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 12:24 bug#13226: 24.3.50; set-file-acl on MS Windows shall check ACL string format Michael Albinus
2012-12-19 14:32 ` Stefan Monnier
2012-12-19 14:38 ` Michael Albinus
2012-12-19 16:25 ` Eli Zaretskii
2012-12-19 16:33 ` Eli Zaretskii
2012-12-19 14:34 ` Stefan Monnier
2012-12-19 14:59 ` Michael Albinus
2012-12-19 15:46 ` Romain Francoise
2012-12-19 15:57 ` Michael Albinus
2012-12-19 16:29 ` Eli Zaretskii
2012-12-19 16:42 ` Romain Francoise
2012-12-19 16:56 ` Eli Zaretskii
2012-12-19 17:44 ` Michael Albinus
2012-12-19 18:36 ` Stefan Monnier
2012-12-19 21:18 ` Eli Zaretskii
2012-12-20 0:53 ` Stefan Monnier
2012-12-22 14:19 ` Eli Zaretskii [this message]
2013-01-04 13:20 ` Michael Albinus
2012-12-19 16:23 ` Eli Zaretskii
2012-12-19 16:55 ` Michael Albinus
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=83y5gqp3ss.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13226@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.