[Bug 8336] --implied-dirs should include the file-list root by default

samba-bugs at samba.org samba-bugs at samba.org
Mon Aug 8 08:49:52 MDT 2011


https://bugzilla.samba.org/show_bug.cgi?id=8336

Wayne Davison <wayned at samba.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #8 from Wayne Davison <wayned at samba.org> 2011-08-08 14:49:51 UTC ---
(In reply to comment #7)
> I cannot imagine any use for avoiding attribute preservation on that
> particular directory.

That's weird, because that has been the desired behavior in all the cases I
have ever used the option.  If I'm copying a particular set of files, I don't
want effects outside of the files I specify.  I might not even have permissions
to tweak the root dir in a situation where a particular set of subdirs was
created for me (e.g. a copy of my home subdir).  The current method lets me
choose to include it or not.  Making it mandatory takes away the user's choice.
 The parent dir may not even be the same dir, e.g. /path1/./some/path
/path2/./another/one -- in such a case, which dir should be the root of the
transfer?  With the current method, the user can choose one, should they so
desire.

As for being unable to specify the permissions that get set on the created
directory, that is true for all instances where the destination directory gets
created when it is outside the transfer (e.g. rsync -ai file1 file2 dest), so
is not something that directly pertains to --relative.  In fact, the --relative
option gives us one way affect it, should we want to do so: rsync -aiR ./file1
./file2 dest.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the rsync mailing list