What |Removed |Added

------- Additional Comments From 2005-11-01 10:10 -------
Just to be clear: rsync already avoids files that it didn't transfer. If you
aren't preserving timestamps (-t), rsync will update files that haven't really
changed (because their modified times differ). You can use the -c (--checksum)
option as one (expensive) way to avoid re-sending files that have not changed
their data, but do not match in modified time.

However, you may be suggesting that rsync be able to check if the updated file
that it just created was created a 100% match of the local file's data. In that
case, it should be possible to go ahead and skip the backup step (as long as
--inplace wasn't specified). We might not even need an option for this (though
I'd need to think about the ramifications of that).

Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
To unsubscribe or change options:
Before posting, read: