From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>, michael.albinus@gmx.de
Cc: thievol@posteo.net, 58919@debbugs.gnu.org
Subject: bug#58919: 28.2; dired-copy-file-recursive fails to overwrite directory
Date: Sat, 17 Dec 2022 10:04:51 +0200 [thread overview]
Message-ID: <83h6xuihgc.fsf@gnu.org> (raw)
In-Reply-To: <fa1fc8c3-f12b-9094-853d-c4ec10b9163c@cs.ucla.edu> (message from Paul Eggert on Fri, 16 Dec 2022 15:22:16 -0800)
> Date: Fri, 16 Dec 2022 15:22:16 -0800
> Cc: thievol@posteo.net, 58919@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> On 12/11/22 02:46, Eli Zaretskii wrote:
> > Paul, did you have an opportunity to come up with the patch you
> > mentioned in this discussion? I'd like to solve this bug for Emacs
> > 29, please.
>
> I hacked on it for a bit and came up with the attached proposed patches
> to the emacs-29 branch. I have not installed them.
>
> These patches address the issues raised by Michael by passing only
> single arguments to make-directory handlers. That way, we don't need to
> worry about whether the handlers follow the new convention. At our
> leisure, perhaps in Emacs 30, we can upgrade the make-directory handlers
> to support the new convention.
Thanks. Looks non-trivial, but I guess we cannot hope for a simpler
fix.
Michael, are you okay with this? do you see any problems, real or
potential, that could endanger the release of Emacs 29?
next prev parent reply other threads:[~2022-12-17 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:54 bug#58919: 28.2; dired-copy-file-recursive fails to overwrite directory Thierry Volpiatto
2022-10-31 13:01 ` Eli Zaretskii
2022-11-01 17:34 ` Thierry Volpiatto
2022-11-01 18:04 ` Paul Eggert
2022-11-01 18:09 ` Eli Zaretskii
2022-11-01 19:21 ` Michael Albinus
2022-12-11 10:46 ` Eli Zaretskii
2022-12-16 23:22 ` Paul Eggert
2022-12-17 8:04 ` Eli Zaretskii [this message]
2022-12-17 9:52 ` Michael Albinus
2022-12-17 10:40 ` Eli Zaretskii
2022-12-17 22:40 ` Paul Eggert
2022-12-18 19:35 ` Michael Albinus
2022-12-18 20:54 ` Paul Eggert
2022-12-23 10:26 ` Michael Albinus
2022-12-24 9:11 ` Paul Eggert
2022-12-24 10:13 ` 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
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=83h6xuihgc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58919@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=michael.albinus@gmx.de \
--cc=thievol@posteo.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).