rsync horribly broken

[Christopher Faylor]

On Fri, Dec 05, 2003 at 09:01:40AM -0800, linda w wrote:
>If that's the case, how did rsync generate the list of files to copy?
>Why would rsync not be able to read them but cp would?  Seems like an
>odd restriction "rsync can read and compare network paths, but can't
>actually open the paths to copy them because it can't understand the
>paths that it created through it's own iteration.

Because it doesn't really understand the // prefix, as I said.  It
probably "optimizes" multiple slashes to one slash at some point in
its filename manipulation.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/