public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: subversion problem
Date: Wed, 25 Apr 2018 17:03:00 -0000	[thread overview]
Message-ID: <e35d02bd-b86f-f045-c48e-beb582a2a44c@acm.org> (raw)
In-Reply-To: <xolh8nzph27.wl-atara-y@mx.scn.tv>

Yasutaka Atarashi wrote:
> I had some doubt that the modification suggested in my mail:
> Cygwin subversion and UNC path https://cygwin.com/ml/cygwin/2018-04/msg00271.html
> would cause the failure.
> However, this would not be the case.

Yes, I agree your change is not the source of the problem.

> 
> I'm afraid to say that it seems to be an oversight in 05-retry-loop.patch.
> 
> The first call of the loop target function must be made BEFORE the call of WIN32_RETRY_LOOP() while Cygwin branch of svn_io_file_rename2() calls WIN32_RETRY_LOOP() directly.

Thanks, I agree this is the likely source of the problem. I won't have time to try it until this weekend. Thanks for investigating.


-- 
David Rothenberger  ----  daveroth@acm.org


--
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:[~2018-04-25 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 20:20 Rockefeller, Harry
2018-04-23 20:31 ` David Rothenberger
2018-04-22 14:04   ` Cygwin subversion and UNC path Yasutaka Atarashi
2018-04-22 15:58     ` David Rothenberger
2018-04-25 13:11     ` subversion problem Yasutaka Atarashi
2018-04-25 17:03       ` David Rothenberger [this message]
2018-04-23 21:28   ` Rockefeller, Harry
2018-04-23 21:05 ` Andrey Repin
2018-04-23 21:28   ` Rockefeller, Harry

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=e35d02bd-b86f-f045-c48e-beb582a2a44c@acm.org \
    --to=daveroth@acm.org \
    --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).