unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: mcenturion@fing.edu.uy, 10897@debbugs.gnu.org
Subject: bug#10897: copy-directory create new directory when copying a symlink
Date: Sun, 22 Aug 2021 16:46:39 +0300	[thread overview]
Message-ID: <8335r1y4lc.fsf@gnu.org> (raw)
In-Reply-To: <87r1elvbzy.fsf@gmx.de> (message from Michael Albinus on Sun, 22 Aug 2021 15:34:57 +0200)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Marco Centurion <mcenturion@fing.edu.uy>,  10897@debbugs.gnu.org
> Date: Sun, 22 Aug 2021 15:34:57 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > FWIW, I think this feature should be controlled by a user option, at
> > least because it changes a very old behavior.  Also, on some systems
> > (MS-Windows, for example) creating a symlink requires non-default
> > privileges, so it could be a nuisance to force this on such users.
> 
> Hmm. Is this something we want also in Tramp?

Which part, specifically?





  reply	other threads:[~2021-08-22 13:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  8:47 bug#10897: copy-directory create new directory when copying a symlink Thierry Volpiatto
2012-02-27  9:11 ` Lars Magne Ingebrigtsen
2012-02-27  9:30   ` Thierry Volpiatto
2012-02-27 10:32     ` Lars Magne Ingebrigtsen
2012-02-27 15:22       ` Thierry Volpiatto
2012-03-09 23:07         ` Lars Magne Ingebrigtsen
2012-03-10  6:08           ` Thierry Volpiatto
2012-03-03  8:42       ` bug#10897: sending mail via report-emacs-bug Thierry Volpiatto
2012-03-03  8:49         ` Eli Zaretskii
2012-03-03  9:29           ` Thierry Volpiatto
2012-03-03 10:04             ` Thierry Volpiatto
2012-03-03 14:29             ` Lars Magne Ingebrigtsen
2012-03-03 14:59               ` Thierry Volpiatto
2012-03-03 15:05                 ` Lars Magne Ingebrigtsen
2012-03-03 17:08                   ` Thierry Volpiatto
2012-03-03 17:20                     ` Thierry Volpiatto
2012-03-04 15:02                       ` Lars Magne Ingebrigtsen
2012-03-05 13:58                         ` Thierry Volpiatto
2012-03-03 14:33         ` Lars Magne Ingebrigtsen
2020-08-25 12:47 ` bug#10897: copy-directory create new directory when copying a symlink Lars Ingebrigtsen
2020-10-13  2:33   ` Lars Ingebrigtsen
2020-10-13  3:15     ` Glenn Morris
2020-10-13  3:19       ` Lars Ingebrigtsen
2021-08-19 21:47 ` Marco Centurion
2021-08-20  1:08 ` Marco Centurion
2021-08-20  5:51   ` Eli Zaretskii
2021-08-22 13:34     ` Michael Albinus
2021-08-22 13:46       ` Eli Zaretskii [this message]
2021-08-22 14:58         ` Michael Albinus
2021-08-22 16:47           ` Eli Zaretskii
2021-08-22 17:13             ` Michael Albinus
2021-08-22 18:48               ` Michael Albinus
2021-08-20 13:44   ` Lars Ingebrigtsen
2021-08-20 14:29     ` Marco Centurion - URI
2021-08-20 14:38       ` Lars Ingebrigtsen

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=8335r1y4lc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=10897@debbugs.gnu.org \
    --cc=mcenturion@fing.edu.uy \
    --cc=michael.albinus@gmx.de \
    /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).