Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 5 Dec 2003 13:01:30 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rsync horribly broken
Message-ID: <20031205180130.GD23244@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <3FD03985.3040604@tlinx.org> <20031205141759.GC8193@redhat.com> <3FD0B9F4.900@tlinx.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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/