all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: thievol@posteo.net, 58919@debbugs.gnu.org
Subject: bug#58919: 28.2; dired-copy-file-recursive fails to overwrite directory
Date: Tue, 01 Nov 2022 20:09:13 +0200	[thread overview]
Message-ID: <83mt9abl86.fsf@gnu.org> (raw)
In-Reply-To: <31dc6bb7-ada3-aeac-c65b-d7de4a326026@cs.ucla.edu> (message from Paul Eggert on Tue, 1 Nov 2022 11:04:22 -0700)

> Date: Tue, 1 Nov 2022 11:04:22 -0700
> Cc: 58919@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 
> The simplest fix I can see is to enhance make-directory so that it 
> returns t if the directory already existed and PARENTS was given, nil on 
> any other successful return. This would require changes to Tramp to 
> avoid races there. I plan to post a proposed patch for comment.

SGTM: make-directory didn't return any meaningful value until now, so
this change should be safe, I think.

Thanks.





  reply	other threads:[~2022-11-01 18:09 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83mt9abl86.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58919@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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 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.