One more output_flist() call that should verify if my analysis
[rsync/rsync.git] / NEWS
CommitLineData
2955529b 1NEWS for rsync 3.0.0 (UNRELEASED)
2dc3db2a 2Protocol: 30 (changed)
2955529b 3Changes since 2.6.9:
36f59b58 4
ac1541f4
WD
5 BUG FIXES:
6
3a72cc29
WD
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.
b4f02871 13
9439c0cb
WD
14 - The code that waits for a child pid now handles being interrupted by a
15 signal. This fixes a problem with the pre-xfer exec function not being
16 able to get the exit status from the script.
3481bdf4 17
d0d0e41f
WD
18 - A negated filter rule now sends the negation option when sending the
19 filter rules.
20
889ae39d
WD
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
8b584075
WD
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
99effefc
WD
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.
e8dad395 31
d762dfe9
WD
32 - Make sure that directory permissions of a newly-created destination
33 directory are handled right when --perms is left off.
34
ac1541f4
WD
35 ENHANCEMENTS:
36
012d1a01
WD
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
9439c0cb
WD
44 the default when talking to older rsync versions), and is compatible with
45 the new incremental recursion mode.
012d1a01 46
9439c0cb
WD
47 - Added the --delete-delay option, which is a more efficient way to delete
48 files at the end of the transfer without needing a separate delete pass.
c7871d98 49
348d54d6
WD
50 - Added the --acls (-A) option to preserve Access Control Lists. This is
51 an improved version of the prior patch that was available. (If you need
52 to have backward compatibility with old, patched versions, the new
53 acls.diff patch that will add that.)
54
55 - Added the --xattrs (-X) option to preserver extended attributes. This is
56 an improved version of the prior patch that was available. (If you need
57 to have backward compatibility with old, patched versions, the new
58 xattrs.diff patch that will add that.)
59
9439c0cb
WD
60 - Added the --fake-super option that allows a non-super user to preserve
61 all attributes of a file by using a special extended-attribute idiom.
62 There is also an analogous "fake super" option for an rsync daemon.
63
332cf6df 64 - Added the --iconv option, which allows rsync to convert filenames from
0156c784
WD
65 one character-set to another during the transfer. The default is to make
66 this feature available as long as your system has iconv_open(). If
67 compilation fails, specify --disable-iconv to configure and rebuild. If
68 you want rsync to perform character-set conversions by default, you can
69 specify --enable-iconv=CONVERT_STRING with the default value for the
70 --iconv option that you wish to use. For example, --enable-iconv=. is a
71 good choice. See the rsync man page for an explanation of the --iconv
72 option's settings.
332cf6df 73
9439c0cb
WD
74 - You may specify --max-delete=0 to a 3.0.0 client as long as the receiving
75 side is at least version 3.0.0. This means that you can pull from an
76 older rsync with this option, but pushing to an older rsync will generate
77 an error. *Be sure to never specify a 0 value to an older rsync client,
78 or it will be silently ignored.*
8adc22e3 79
3a5a7de6 80 - The --hard-link option now uses less memory on both the sending and
9439c0cb
WD
81 receiving side for all protocol versions. For protocol 30, the use of a
82 hashtable on the sending side allows us to more efficiently convey to the
83 receiver what files are linked together. This reduces the amount of data
84 sent over the socket by a considerable margin (rather than adding more
85 data), and limits the in-memory storage of the device+inode information
86 to just the sending side for the new protocol 30, or to the receiving
87 side when speaking an older protocol (note that older rsync versions kept
88 the device+inode information on both sides).
3a5a7de6 89
4968423e
WD
90 INTERNAL:
91
348d54d6
WD
92 - Rsync now supports the transfer of 64-bit timestamps (time_t values).
93
94 - Fixed a build problem with older (2.x) versions of gcc.
95
4d2ea5a8
WD
96 - Added some isType() functions that make dealing with signed characters
97 easier without forcing variables via casts.
98
3a72cc29
WD
99 - Upgraded the included popt version to 1.10.2 and improved its use of
100 string-handling functions.
418da6d9 101
d0d0e41f
WD
102 - Added missing prototypes for compatibility functions from the lib dir.
103
c7871d98
WD
104 - Configure determines if iconv() has a const arg, allowing us to avoid a
105 compiler warning.
106
107 - Made the sending of some numbers more efficient for protocol 30.
d0d0e41f 108
d762dfe9
WD
109 - Make sure that a daemon process doesn't mind if the client was weird and
110 omitted the --server option.
111
d0d0e41f
WD
112 - Improved the use of "const" on pointers.
113
7c329ec7
WD
114 DEVELOPER RELATED:
115
348d54d6
WD
116 - Rsync now has a way of handling protocol-version changes during the
117 development of a new protocol version. This exchange of sub-version
118 info does not interfere with the {MIN,MAX}_PROTOCOL_VERSION checking
119 in older versions (which would be the case if every minor change made
120 to the protocol in CVS incremented the main PROTOCOL_VERSION value).