| | 1 | NEWS for rsync 3.0.0 (UNRELEASED) |
| | 2 | Protocol: 30 (changed) |
| | 3 | Changes since 2.6.9: |
| | 4 | |
| | 5 | BUG FIXES: |
| | 6 | |
| | 7 | - Fixed the output of -ii when combined with one of the --*-dest options: |
| | 8 | it now itemizes all the items, not just the changed ones. |
| | 9 | |
| | 10 | - Made the output of all file types consistent when using a --*-dest |
| | 11 | option. Prior versions used to output too many creation events for |
| | 12 | matching items. |
| | 13 | |
| | 14 | - The code that waits for a child pid now handles being interrupted by |
| | 15 | a signal. This fixes a problem with the pre-xfer exec function not |
| | 16 | being able to get the exit status from the script. |
| | 17 | |
| | 18 | - A negated filter rule now sends the negation option when sending the |
| | 19 | filter rules. |
| | 20 | |
| | 21 | - Fixed a problem with the --out-format (aka --log-format) option: it |
| | 22 | would output superfluous directory information for a non-daemon rsync. |
| | 23 | |
| | 24 | - Fixed a problem with -vv (double --verbose) and --stats when "pushing" |
| | 25 | files (which includes local copies). Version 2.6.9 would complete the |
| | 26 | copy, but exit with an error when the receiver output its memory stats. |
| | 27 | |
| | 28 | - If --password-file is used on a non-daemon transfer, rsync now complains |
| | 29 | and exits. This should help users figure out that they can't use this |
| | 30 | option to control a remote shell's password prompt. |
| | 31 | |
| | 32 | - Make sure that directory permissions of a newly-created destination |
| | 33 | directory are handled right when --perms is left off. |
| | 34 | |
| | 35 | ENHANCEMENTS: |
| | 36 | |
| | 37 | - A new incremental-recursion algorithm is now used when rsync is talking |
| | 38 | to another 3.0.0 version. This starts the transfer going more quickly |
| | 39 | (before all the files have been found), and requires much less memory. |
| | 40 | See the --recursive option in the manpage for some restrictions. |
| | 41 | |
| | 42 | - The default --delete algorithm is now --delete-during when talking to a |
| | 43 | 3.x rsync. This is a faster scan than using --delete-before (which is |
| | 44 | the default when talking to older rsync versions), and is compatible |
| | 45 | with the new incremental recursion mode. |
| | 46 | |
| | 47 | - Added the --delete-delay option, which is a more efficient way to |
| | 48 | delete files at the end of the transfer without needing a separate |
| | 49 | delete pass. |
| | 50 | |
| | 51 | - Added the --acls (-A) option to preserve Access Control Lists. This is |
| | 52 | an improved version of the prior patch that was available. (If you need |
| | 53 | to have backward compatibility with old, patched versions, the new |
| | 54 | acls.diff patch that will add that.) |
| | 55 | |
| | 56 | - Added the --xattrs (-X) option to preserver extended attributes. This is |
| | 57 | an improved version of the prior patch that was available. (If you need |
| | 58 | to have backward compatibility with old, patched versions, the new |
| | 59 | xattrs.diff patch that will add that.) |
| | 60 | |
| | 61 | - You may specify --max-delete=0 to a 3.0.0 client as long as the |
| | 62 | receiving side is at least version 3.0.0. This means that you |
| | 63 | can pull from an older rsync with this option, but pushing to an |
| | 64 | older rsync will generate an error. *Be sure to never specify a 0 |
| | 65 | value to an older rsync client, or it will be silently ignored.* |
| | 66 | |
| | 67 | - The --hard-link option now uses less memory on both the sending and |
| | 68 | receiving side for all protocol versions. For protocol 30, the use |
| | 69 | of a hashtable on the sending side allows us to more efficiently |
| | 70 | convey to the receiver what files are linked together. This reduces |
| | 71 | the amount of data sent over the socket by a considerable margin |
| | 72 | (rather than adding more data), and limits the in-memory storage of |
| | 73 | the device+inode information to just the sending side for the new |
| | 74 | protocol 30, or to the receiving side when speaking an older protocol |
| | 75 | (note that older rsync versions kept the device+inode information on |
| | 76 | both sides). |
| | 77 | |
| | 78 | INTERNAL: |
| | 79 | |
| | 80 | - Rsync now supports the transfer of 64-bit timestamps (time_t values). |
| | 81 | |
| | 82 | - Fixed a build problem with older (2.x) versions of gcc. |
| | 83 | |
| | 84 | - Added some isType() functions that make dealing with signed characters |
| | 85 | easier without forcing variables via casts. |
| | 86 | |
| | 87 | - Upgraded the included popt version to 1.10.2 and improved its use of |
| | 88 | string-handling functions. |
| | 89 | |
| | 90 | - Added missing prototypes for compatibility functions from the lib dir. |
| | 91 | |
| | 92 | - Configure determines if iconv() has a const arg, allowing us to avoid a |
| | 93 | compiler warning. |
| | 94 | |
| | 95 | - Made the sending of some numbers more efficient for protocol 30. |
| | 96 | |
| | 97 | - Make sure that a daemon process doesn't mind if the client was weird and |
| | 98 | omitted the --server option. |
| | 99 | |
| | 100 | - Improved the use of "const" on pointers. |
| | 101 | |
| | 102 | DEVELOPER RELATED: |
| | 103 | |
| | 104 | - Rsync now has a way of handling protocol-version changes during the |
| | 105 | development of a new protocol version. This exchange of sub-version |
| | 106 | info does not interfere with the {MIN,MAX}_PROTOCOL_VERSION checking |
| | 107 | in older versions (which would be the case if every minor change made |
| | 108 | to the protocol in CVS incremented the main PROTOCOL_VERSION value). |
Matt McCutchen's Web Site / rsync / rsync.git / blame_incremental