rsync - Oct 2006 - DO NOT REPLY [Bug 4195] New: "--list-only" option has an off-by-one error and misses out the last file of the list

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

           Summary: "--list-only" option has an off-by-one error and
misses
                    out the last file of the list
           Product: rsync
           Version: 2.6.8
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: rsync_spam@i-am-free.net
         QAContact: rsync-qa@samba.org


Observed in version 2.6.8 on Linux.

$ ls -l
total 0
-rw------- 1 tom tom 0 Oct 29 17:34 a
-rw------- 1 tom tom 0 Oct 29 17:34 b
-rw------- 1 tom tom 0 Oct 29 17:34 c

$ rsync --list-only *
-rw-------           0 2006/10/29 17:34:49 a
-rw-------           0 2006/10/29 17:34:49 b

The "--dry-run --verbose" combination of options seems to work
correctly.


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


rsync_spam@i-am-free.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #1 from rsync_spam@i-am-free.net  2006-10-29 11:52 MST -------
Ah. Not a bug. Last argument is still taken as a destination, so 
"rsync --list-only ." works correctly.

It may useful to check for the mistaken use of "*"... but that's
nothing to do
with --list-only. The only connection is that --listonly works both with and
without a destination argument.


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