From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Subject: Re: copy-directory
Date: Tue, 06 Oct 2009 19:26:36 +0200 [thread overview]
Message-ID: <87pr90wi0j.fsf@gmx.de> (raw)
In-Reply-To: <87ab06p925.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 05 Oct 2009 09:57:22 +0200")
David Kastrup <dak@gnu.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> Or shall we remove PRESERVE-UID-GID from `copy-directory'?
>>
>> I guess we can remove it for now,
>
> I think that UID/GID should transparently be preserved when copying
> directories whenever possible (in particular when using /sudo:: methods
> or similar). I don't think that there is an important usage case for
> "don't preserve UID/GID even if you could": it would likely imply
> copying a tree and turning it into root/root possession on today's
> systems.
Although it is not on my top priority, I would second David. A primitive
function `set-file-owner' would not harm, if it is explicitely said in
the docstring, that it works only in the cases the underlying OS
supports it.
And a Tramp file name handler could be called for this, useful at least
for "su" and "sudo" connections.
What I'm curious: does change ownership work for other systems, like
Win32? The smbclient, used in Tramp for "smb" connections, offers a
chown subcommand ... maybe it is applicable only, if there is a Samba
server at the other end.
Best regards, Michael.
next prev parent reply other threads:[~2009-10-06 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8763avuyt3.fsf@gmx.de>
[not found] ` <83zl87nw88.fsf@gnu.org>
2009-10-04 16:41 ` copy-directory Stefan Monnier
2009-10-04 20:02 ` copy-directory Michael Albinus
2009-10-05 3:13 ` copy-directory Stefan Monnier
2009-10-05 7:22 ` copy-directory Michael Albinus
2009-10-05 7:57 ` copy-directory David Kastrup
2009-10-06 17:26 ` Michael Albinus [this message]
2009-10-06 18:50 ` copy-directory Eli Zaretskii
2009-10-04 19:58 ` copy-directory Michael Albinus
2009-10-04 21:31 ` copy-directory Eli Zaretskii
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=87pr90wi0j.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
/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).