- - Added better checking of the checksum-header values that come over
- the socket.
-
- - Merged a variety of file-deleting functions into a single function so
- that it is easier to maintain.
-
- - Improved the type of some variables (particularly blocksize vars) for
- consistency and proper size.
-
- - Got rid of the uint64 type (which we didn't need).
-
- - Use a slightly more compatible set of core #include directives.
-
- - Defined int32 in a way that ensures that the build dies if we can't
- find a variable with at least 32 bits.
-
- - The daemon's "read only" config item now sets an internal read_only
- variable that makes extra sure that no write/delete calls on the
- read-only side can succeed.
-
- PROTOCOL DIFFERENCES FOR VERSION 29:
-
- - A 16-bit flag-word is transmitted after every file-list index. This
- indicates what is changing between the sender and the receiver. The
- generator now transmits an index and a flag-word to indicate when
- dirs and symlinks have changed (instead of producing a message),
- which makes the outputting of the information more consistent and
- less prone to screen corruption (because the local receiver/sender is
- now outputting all the file-change info messages).
-
- - If a file is being hard-linked, the appropriate bit is enabled in
- the flag-word and the name of the file that was linked immediately
- follows in vstring format (see below).
-
- - If a file is being transferred with an alternate-basis file, the
- appropriate bit is enabled in the flag-word and a single-byte
- follows, indicating what type of basis file was chosen. If that
- indicates that a fuzzy-match was selected, the name of the match
- immediately follows in vstring format. A vstring is a variable
- length string that has its size written prior to the string, and
- no terminating null. If the string is from 1-127 bytes, the length
- is a single byte. If it is from 128-32767 bytes, the length is
- written as ((len >> 8) | 0x80) followed by (len % 0x100).
-
- - The sending of exclude names is done using filter-rule syntax. This
- means that all names have a prefixed rule indicator, even excludes
- (which used to be sent as a bare pattern, when possible). The -C
- option will include the per-dir .cvsignore merge file in the list of
- filter rules so it is positioned correctly (unlike in some older
- transfer scenarios).
-
- - Rsync sorts the filename list in a different way: it sorts the subdir
- names after the non-subdir names for each dir's contents, and it
- always puts a dir's contents immediately after the dir's name in the
- list. (Previously an item named "foo.txt" would sort in between
- directory "foo/" and "foo/bar".)
-
- - When talking to a protocol 29 rsync daemon, a list-only request
- is able to note this before the options are sent over the wire and
- the new --list-only option is included in the options.
-
- - When the --stats bytes are sent over the wire (or stored in a batch),
- they now include two elapsed-time values: one for how long it took to
- build the file-list, and one for how long it took to send it over the
- wire (each expressed in thousandths of a second).
-
- - When --delete-excluded is specified with some filter rules (AKA
- excludes), a client sender will now initiate a send of the rules to
- the receiver (older protocols used to omit the sending of excludes in
- this situation since there were no receiver-specific rules that
- survived --delete-excluded back then). Note that, as with all the
- filter-list sending, only items that are significant to the other
- side will actually be sent over the wire, so the filter-rule list
- that is sent in this scenario is often empty.
-
- - An index equal to the file-list count is sent as a keep-alive packet
- from the generator to the sender, which then forwards it on to the
- receiver. This normally invalid index is only a valid keep-alive
- packet if the 16-bit flag-word that follows it contains a single bit
- (ITEM_IS_NEW, which is normally an illegal flag to appear alone).