From: Philipp Stephani <p.stephani2@gmail.com>
To: Aaron Jensen <aaronjensen@gmail.com>, 28483@debbugs.gnu.org
Subject: bug#28483: [PATCH] Fix copy-directory creating missing directory
Date: Mon, 18 Sep 2017 17:40:15 +0000 [thread overview]
Message-ID: <CAArVCkQZmSVfzRmaV8Ot-+eZHbgA2UohhqBHjUA7SvevOL-jkw@mail.gmail.com> (raw)
In-Reply-To: <CAHyO48wW_sZLZkm9kdtaO7KmzFtYx_6Y7BgKu8tmCroO+quEEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Aaron Jensen <aaronjensen@gmail.com> schrieb am So., 17. Sep. 2017 um
22:19 Uhr:
>
> I’m not sure what Emac’s principles are on it, but perhaps an error
> pointing to this change when attempting to copy to a non-existing
> directory would help people in the future as well since this is a
> change in behavior to an existing function w/o a deprecation.
>
>
I think copy-directory is mostly used by libraries, so alerting the user
wouldn't help: the problem is in the libraries that invoke copy-directory.
That the behavior changed is unfortunate, but unavoidable due to security
concerns. The behavior changes are mentioned in NEWS.
[-- Attachment #2: Type: text/html, Size: 943 bytes --]
next prev parent reply other threads:[~2017-09-18 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 19:10 bug#28483: 26.0.50; copy-directory does not create directories Aaron Jensen
2017-09-17 19:15 ` bug#28483: [PATCH] Fix copy-directory creating missing directory Aaron Jensen
2017-09-17 19:48 ` Philipp Stephani
2017-09-17 20:19 ` Aaron Jensen
2017-09-18 17:40 ` Philipp Stephani [this message]
2017-09-17 19:20 ` bug#28483: 26.0.50; copy-directory does not create directories Aaron Jensen
2017-09-17 20:40 ` Paul Eggert
2017-09-17 23:12 ` Aaron Jensen
2017-09-17 23:52 ` Paul Eggert
2017-09-20 11:26 ` Eli Zaretskii
2017-09-20 18:59 ` bug#28520: " Paul Eggert
2017-09-20 19:54 ` Eli Zaretskii
2017-09-20 23:04 ` Adam Plaice
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=CAArVCkQZmSVfzRmaV8Ot-+eZHbgA2UohhqBHjUA7SvevOL-jkw@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=28483@debbugs.gnu.org \
--cc=aaronjensen@gmail.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.