batch doesn't have.
- Tweaked the "skipping ..." message that is output for already-
  applied batched updates.

the report happens after all --delete-after activity has ceased when
pulling, and (2) a batch-file created when pushing gets the stats
values written out prior to any end-of-run keep-alive packets.

to take an integer count instead of a struct file_list so that we
can pass in a file-list-count offset for delete's separate calls
to send_directory().

--delete-during and --fuzzy don't get any superfluous
" N files..." lines output in the middle of the processing.

the same time to avoid a useless round-trip delay for an empty
delay-updates phase.

safely removed for the next release).

to get rid of it later on.

pre-release versions.

the opposite of what they should be.

- Added the saving of the --compress option's state.
- Deal with the xfer_dirs var in a better way for pre-29 batches.

  or --write-batch.
- If --write-batch is combined with --dry-run, just disable
  --write-batch (that avoids trying to create a batch file
  and tells the user what would be transferred).

transfer data.

to re-run the script while pretending to be root.

in find_filename_suffix().

the receiver's delay-update processing.

the daemon can't open the log-file.

  by both the sender and the receiver).
- Added an extra phase to the end of the transfer to better handle
  delayed updates that have hard links.

delayed updates that have hard links.

  delayed updates that have hard links.
- Send the new ITEM_DUMMY_BIT to the sender so that we can figure
  out if the other side is pre1 or pre2 and let the receiver reject
  it.