X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/348d54d6d18e7a83b91735d063daac7856519e4e..044dc293071c635129afdedad63f30c2d49cd942:/NEWS diff --git a/NEWS b/NEWS index eae08d90..7b0a7e1b 100644 --- a/NEWS +++ b/NEWS @@ -11,9 +11,9 @@ Changes since 2.6.9: option. Prior versions used to output too many creation events for matching items. - - The code that waits for a child pid now handles being interrupted by - a signal. This fixes a problem with the pre-xfer exec function not - being able to get the exit status from the script. + - The code that waits for a child pid now handles being interrupted by a + signal. This fixes a problem with the pre-xfer exec function not being + able to get the exit status from the script. - A negated filter rule now sends the negation option when sending the filter rules. @@ -32,6 +32,9 @@ Changes since 2.6.9: - Make sure that directory permissions of a newly-created destination directory are handled right when --perms is left off. + - Improved --hard-link so that more corner cases are handled correctly + when combined with options such as --link-dest and/or --ignore-existing. + ENHANCEMENTS: - A new incremental-recursion algorithm is now used when rsync is talking @@ -41,12 +44,11 @@ Changes since 2.6.9: - The default --delete algorithm is now --delete-during when talking to a 3.x rsync. This is a faster scan than using --delete-before (which is - the default when talking to older rsync versions), and is compatible - with the new incremental recursion mode. + the default when talking to older rsync versions), and is compatible with + the new incremental recursion mode. - - Added the --delete-delay option, which is a more efficient way to - delete files at the end of the transfer without needing a separate - delete pass. + - Added the --delete-delay option, which is a more efficient way to 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 @@ -58,25 +60,53 @@ Changes since 2.6.9: 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 - older rsync will generate an error. *Be sure to never specify a 0 - value to an older rsync client, or it will be silently ignored.* + - Added the --fake-super option that allows a non-super user to preserve + all attributes of a file by using a special extended-attribute idiom. + There is also an analogous "fake super" option for an rsync daemon. + + - Added the --iconv option, which allows rsync to convert filenames from + one character-set to another during the transfer. The default is to make + this feature available as long as your system has iconv_open(). If + compilation fails, specify --disable-iconv to configure and rebuild. If + you want rsync to perform character-set conversions by default, you can + specify --enable-iconv=CONVERT_STRING with the default value for the + --iconv option that you wish to use. For example, --enable-iconv=. is a + good choice. See the rsync man page for an explanation of the --iconv + option's settings. + + - Added the --skip-compress=LIST option to override of the default list of + file suffixes that will not be compressed when using --compress. + + - The --max-delete option now outputs a warning if it skipped any file + deletions, including a count of how many deletions were skipped. (Older + versions just silently stopped deleting things.) + + - You may specify --max-delete=0 to a 3.0.0 client to request that it warn + about any files that it wants to delete without deleting anything. If + you're not sure what version the client is, you can use the less-obvious + --max-delete=-1, as old and new versions will both treat that as the + same request (though older versions don't warn). - The --hard-link option now uses less memory on both the sending and - receiving side for all protocol versions. For protocol 30, the use - of a hashtable on the sending side allows us to more efficiently - convey to the receiver what files are linked together. This reduces - the amount of data sent over the socket by a considerable margin - (rather than adding more data), and limits the in-memory storage of - the device+inode information to just the sending side for the new - protocol 30, or to the receiving side when speaking an older protocol - (note that older rsync versions kept the device+inode information on - both sides). + receiving side for all protocol versions. For protocol 30, the use of a + hashtable on the sending side allows us to more efficiently convey to the + receiver what files are linked together. This reduces the amount of data + sent over the socket by a considerable margin (rather than adding more + data), and limits the in-memory storage of the device+inode information + to just the sending side for the new protocol 30, or to the receiving + side when speaking an older protocol (note that older rsync versions kept + the device+inode information on both sides). + + - A lot more --no-OPTION override options are now supported. INTERNAL: + - The file-list sorting algorithm now uses a sort that keeps any same- + named items in the same order as they were specified. This allows + rsync to always ensure that the first of the duplicates is the one + that will be included in the copy. The new sort was also faster + than the glibc version of qsort() and mergesort() in my testing. + - Rsync now supports the transfer of 64-bit timestamps (time_t values). - Fixed a build problem with older (2.x) versions of gcc. @@ -99,8 +129,13 @@ Changes since 2.6.9: - Improved the use of "const" on pointers. + - Improved J.W.'s pool_alloc routines to add a way of freeing older + sections of a pool's memory. + DEVELOPER RELATED: + - Rsync is now licensed under the GPLv3 or later. + - 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