https://bugzilla.samba.org/show_bug.cgi?id=2390 ------- Additional Comments From woodd@deshaw.com 2005-02-24 17:21 ------- Created an attachment (id=980) --> (https://bugzilla.samba.org/attachment.cgi?id=980&action=view) Proposed sender.c / receiver.c patch -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
https://bugzilla.samba.org/show_bug.cgi?id=2390
wayned@samba.org changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX
------- Additional Comments From wayned@samba.org  2005-02-24 19:39 -------
The purpose of the --dry-run is to tell you what would be transferred.  The
output of the names is exactly that: the file being mentioned normally means
"this file has been transferred", but with --dry-run it instead means
"this file
would be transferred".  The stats follow in this same vein:  how many files
would have been transferred and how large are they?
-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Apparently Analagous Threads
- [Bug 2390] New: some dry run stats inaccurate
- [Bug 2389] block/character devices on Solaris yield wacky rsync stats
- [Bug 2389] New: block/character devices on Solaris yield wacky rsync stats
- DO NOT REPLY [Bug 4412] New: --dry-run output inaccurate due to implied symlink
- DO NOT REPLY [Bug 5404] New: rsync --dry-run should show where files will go