Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 5 Dec 2003 13:01:30 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: rsync horribly broken
Message-ID:	<20031205180130.GD23244@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3FD03985 DOT 3040604 AT tlinx DOT org> <20031205141759 DOT GC8193 AT redhat DOT com> <3FD0B9F4 DOT 900 AT tlinx DOT org>
Mime-Version:	1.0
In-Reply-To:	<3FD0B9F4.900@tlinx.org>
User-Agent:	Mutt/1.4.1i

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/

- Raw text -