rsync - Feb 2008 - DO NOT REPLY [Bug 5266] New: Duplicate "not creating new directory" output w/ incremental recursion

https://bugzilla.samba.org/show_bug.cgi?id=5266

           Summary: Duplicate "not creating new directory" output w/
                    incremental recursion
           Product: rsync
           Version: 3.0.0
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: matt@mattmccutchen.net
         QAContact: rsync-qa@samba.org


With --ignore-non-existing and incremental recursion, rsync prints the "not
creating new directory" verbose message twice for each directory.  This is
because directories are visited twice in incremental recursion.  A test needs
to be added to only print the message on one of the visits.

$ mkdir src src/subdir dest
$ rsync -r --ignore-non-existing -vv src/ dest/
sending incremental file list
delta-transmission disabled for local transfer or --whole-file
not creating new directory "subdir"
not creating new directory "subdir"
total: matches=0  hash_hits=0  false_alarms=0 data=0

sent 46 bytes  received 16 bytes  124.00 bytes/sec
total size is 0  speedup is 0.00


-- 
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=5266


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #1 from wayned@samba.org  2008-02-18 01:58 CST -------
This is fixed in the dev version.


-- 
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.