Wayne,
I noticed that you quietly removed the compatibility mode for sending
ACLs to rsyncs before 2.6.8 in revision 1.169 of acls.diff. It would
be good to document this in the man page. A metapatch to acls.diff
that revises the documentation in rsync.yo is attached; I didn't
regenerate rsync.1 because I don't have yodl 2 set up. Where did you
get the version of yodl 2 that you are using for rsync man pages?
Matt
### Eclipse Workspace Patch 1.0
#P rsync
Index: patches/acls.diff
===================================================================
RCS file: /cvsroot/rsync/patches/acls.diff,v
retrieving revision 1.178
diff -u -r1.178 acls.diff
--- patches/acls.diff 15 Dec 2006 23:05:02 -0000 1.178
+++ patches/acls.diff 16 Dec 2006 02:39:52 -0000
@@ -6065,7 +6065,7 @@
dit(bf(-E, --executability)) This option causes rsync to preserve the
executability (or non-executability) of regular files when bf(--perms) is
-@@ -805,6 +810,15 @@ quote(itemization(
+@@ -805,6 +810,17 @@ quote(itemization(
If bf(--perms) is enabled, this option is ignored.
@@ -6073,15 +6073,17 @@
+ACLs to be the same as the source ACLs. This nonstandard option only
+works if the remote rsync also supports it. bf(--acls) implies bf(--perms).
+
-+Note also that an optimization of the ACL-sending protocol used by this
-+version makes it incompatible with sending files to an older ACL-enabled
-+rsync unless you double the bf(--acls) option (e.g. bf(-AA)). This
-+doubling is not needed when pulling files from an older rsync.
++In version 2.6.8, rsync began to send ACLs in an optimized format; rsyncs
++older than 2.6.8 do not understand this format. Thus, a post-2.6.8 rsync
++cannot preserve ACLs when sending files to a pre-2.6.8 rsync.
++Rsync 2.6.8 had an option to send ACLs in the old format for compatibility,
++but this option was removed in 3.0.0. The format change does not affect
++preserving ACLs from a pre-2.6.8 rsync to a post-2.6.8 rsync.
+
dit(bf(--chmod)) This option tells rsync to apply one or more
comma-separated "chmod" strings to the permission of the files in the
transfer. The resulting value is treated as though it was the permissions
-@@ -1402,8 +1416,8 @@ if the receiving rsync is at least versi
+@@ -1402,8 +1418,8 @@ if the receiving rsync is at least versi
with older versions of rsync, but that also turns on the output of other
verbose messages).
@@ -6092,7 +6094,7 @@
type of update being done, bf(X) is replaced by the file-type, and the
other letters represent attributes that may be output if they are being
modified.
-@@ -1452,7 +1466,11 @@ quote(itemization(
+@@ -1452,7 +1468,11 @@ quote(itemization(
sender's value (requires bf(--owner) and super-user privileges).
it() A bf(g) means the group is different and is being updated to the
sender's value (requires bf(--group) and the authority to set the group).
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
