From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: copy-directory Date: Mon, 05 Oct 2009 09:57:22 +0200 Organization: Organization?!? Message-ID: <87ab06p925.fsf@lola.goethe.zz> References: <8763avuyt3.fsf@gmx.de> <83zl87nw88.fsf@gnu.org> <87y6nr2aho.fsf@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1254729532 26562 80.91.229.12 (5 Oct 2009 07:58:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Oct 2009 07:58:52 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 05 09:58:47 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MuiT0-0003dF-KF for ged-emacs-devel@m.gmane.org; Mon, 05 Oct 2009 09:58:46 +0200 Original-Received: from localhost ([127.0.0.1]:50530 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MuiT0-0002Tj-On for ged-emacs-devel@m.gmane.org; Mon, 05 Oct 2009 03:58:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MuiSE-00024I-6j for emacs-devel@gnu.org; Mon, 05 Oct 2009 03:57:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MuiS9-00021G-HG for emacs-devel@gnu.org; Mon, 05 Oct 2009 03:57:57 -0400 Original-Received: from [199.232.76.173] (port=41589 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MuiS9-000211-BR for emacs-devel@gnu.org; Mon, 05 Oct 2009 03:57:53 -0400 Original-Received: from mx20.gnu.org ([199.232.41.8]:14161) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MuiS8-0002gX-RM for emacs-devel@gnu.org; Mon, 05 Oct 2009 03:57:53 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MuiS7-0001tt-8q for emacs-devel@gnu.org; Mon, 05 Oct 2009 03:57:51 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1MuiS3-0003CC-0z for emacs-devel@gnu.org; Mon, 05 Oct 2009 09:57:47 +0200 Original-Received: from p5b2c214a.dip.t-dialin.net ([91.44.33.74]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Oct 2009 09:57:47 +0200 Original-Received: from dak by p5b2c214a.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Oct 2009 09:57:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 20 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c214a.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:0JfzQ2R/j676cDXuGJj/tLnoP5A= X-detected-operating-system: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:115910 Archived-At: Stefan Monnier 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. I would like to add that before the time of disk quotas, the owner of a file was always able to do chown/chgrp on files (this cleared the setuid bit for security reasons, but that was it). It was the usual way of passing data to somebody else (and nobody other). -- David Kastrup