X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/051ad69634a961188a09453b33abe605c2a55bd6..753849fdbcf8df0a408135be469f620bb74f2ab5:/NEWS diff --git a/NEWS b/NEWS index 3d51c537..eae08d90 100644 --- a/NEWS +++ b/NEWS @@ -29,6 +29,9 @@ Changes since 2.6.9: and exits. This should help users figure out that they can't use this option to control a remote shell's password prompt. + - Make sure that directory permissions of a newly-created destination + directory are handled right when --perms is left off. + ENHANCEMENTS: - A new incremental-recursion algorithm is now used when rsync is talking @@ -45,6 +48,16 @@ Changes since 2.6.9: delete files at the end of the transfer without needing a separate delete pass. + - Added the --acls (-A) option to preserve Access Control Lists. This is + an improved version of the prior patch that was available. (If you need + to have backward compatibility with old, patched versions, the new + acls.diff patch that will add that.) + + - Added the --xattrs (-X) option to preserver extended attributes. This is + an improved version of the prior patch that was available. (If you need + to have backward compatibility with old, patched versions, the new + xattrs.diff patch that will add that.) + - You may specify --max-delete=0 to a 3.0.0 client as long as the receiving side is at least version 3.0.0. This means that you can pull from an older rsync with this option, but pushing to an @@ -64,6 +77,10 @@ Changes since 2.6.9: INTERNAL: + - Rsync now supports the transfer of 64-bit timestamps (time_t values). + + - Fixed a build problem with older (2.x) versions of gcc. + - Added some isType() functions that make dealing with signed characters easier without forcing variables via casts. @@ -77,8 +94,15 @@ Changes since 2.6.9: - Made the sending of some numbers more efficient for protocol 30. + - Make sure that a daemon process doesn't mind if the client was weird and + omitted the --server option. + - Improved the use of "const" on pointers. DEVELOPER RELATED: - - ... + - Rsync now has a way of handling protocol-version changes during the + development of a new protocol version. This exchange of sub-version + info does not interfere with the {MIN,MAX}_PROTOCOL_VERSION checking + in older versions (which would be the case if every minor change made + to the protocol in CVS incremented the main PROTOCOL_VERSION value).