X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/0e5dd898669f2b2f272079320fdc71155008155a..7b9598b2d5d0aa6aefe06731dc60612ee98646da:/NEWS diff --git a/NEWS b/NEWS index 23d5fd63..51049d5f 100644 --- a/NEWS +++ b/NEWS @@ -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 @@ -71,6 +74,9 @@ Changes since 2.6.9: 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. + - 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 @@ -94,8 +100,8 @@ Changes since 2.6.9: - 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 GNU C version of qsort() (and mergesort() too) in my testing. + 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). @@ -119,8 +125,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