public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: svn
Date: Mon, 14 Feb 2011 14:37:00 -0000	[thread overview]
Message-ID: <4D593E24.6060208@cs.umass.edu> (raw)
In-Reply-To: <ijb6va$soi$1@dough.gmane.org>

On 2/14/2011 7:25 AM, Gary wrote:
> Eliot Moss wrote:
>> On 2/14/2011 3:11 AM, Gary wrote:
>>> David Rothenberger wrote:
>>>> If the files checked out in both directories are byte-for-byte
>> identical
>>>> (including binary files), I can't see how svn could be the culprit.
>>>
>>> If I can replace svn in the sequence with something else, for example
>>> tortoise, and everything then works, then Cygwin/svn *is* the culprit.
>>
>> Not necessarily ... it could be the underlying ssh, if you are using
>> svn over ssh, and it could be BLODA interfering with cygwin ...
>
> And yet not doing it with another client? It's not really very likely,
> is it?

In the fall of 2009 I was having a problem with rsync over ssh.
Corinna and I got to the bottom of it: BLODA interfering with
proper operation of socketpair. In the process, I found that if
I disabled socketpair manually in the output of /.configure for
building rsync, forcing it to use pipes instead, it worked fine.

We have had occasional but persistent queries here about git
over ssh, and you are reporting issues with svn and ssh. I am
wondering if it has something to do with the sockets/pipes
used to communicate between svn or git and the ssh subprocess.

Best wishes -- EM

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

  reply	other threads:[~2011-02-14 14:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 15:45 svn Gary
2011-02-10 15:50 ` svn Eliot Moss
2011-02-10 20:03   ` svn Gary
2011-02-10 20:54     ` svn David Rothenberger
2011-02-11  8:09       ` svn Gary
2011-02-11 12:01         ` svn Eliot Moss
2011-02-11 16:28         ` svn David Rothenberger
2011-02-14  8:12           ` svn Gary
2011-02-14 12:01             ` svn Eliot Moss
2011-02-14 12:25               ` svn Gary
2011-02-14 14:37                 ` Eliot Moss [this message]
2011-02-14 14:44                   ` svn Gary
2011-02-14 16:18                     ` svn Eliot Moss
2011-02-14 17:33             ` svn David Rothenberger
2011-02-15 11:09               ` svn Gary
2011-02-15 16:16                 ` svn David Rothenberger
2011-02-11  2:15     ` svn Eliot Moss
2011-02-11  4:20       ` svn Larry Hall (Cygwin)
2011-02-11  4:21         ` svn Eliot Moss
2011-02-11  7:24           ` svn Gary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D593E24.6060208@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).