Message-ID: <4AF6F019.2050506@monai.ca>
Date: Sun, 08 Nov 2009 08:21:45 -0800
From: Steven Monai <steve+cygwin AT monai DOT ca>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Problem with rsync 3.0.6-1 under 1.7.0-62 and 63
References: <4AF5A3B3 DOT 7010403 AT monai DOT ca> <4AF5AD99 DOT 2040305 AT cs DOT umass DOT edu> <4AF5C2E1 DOT 6010701 AT monai DOT ca> <4AF5FB1D DOT 5010609 AT cs DOT umass DOT edu> <4AF64CDD DOT 7000405 AT monai DOT ca> <4AF67C20 DOT 8060707 AT cs DOT umass DOT edu> <4AF6DE22 DOT 6080402 AT cs DOT umass DOT edu>
In-Reply-To: <4AF6DE22.6080402@cs.umass.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Eliot Moss wrote:
>  There does
> not seem to be anything like this reported in the rsync list,
> so I think it's particular to cygwin, and probably to 1.7.x.

I really think you should report what you're seeing to the rsync mailing
list. It is entirely possible that no one who has run your particular
use case before (rsync v3.0.6 failing to work with rsync v2.6.8, and
vice versa) has ever gone to the extra effort of reporting the problem.

In the best case, the rsync gurus may be able to look at your error
codes and tell right away what is going wrong. They may even agree with
your assessment that Cygwin is somehow to blame, although I'd lean more
towards a protocol mismatch hypothesis.

-SM
--

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