[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Windows XP "Access denied" svn_io_rename

From: Steve Dwire <sdwire_at_pcsigroup.com>
Date: 2003-10-20 20:12:37 CEST

Aha. It is there in the FAQ. I guess I kind of viewed IssueTracker as
"the" place to track things that need to be addressed for a particular
release of Subversion. The workaround presented in the FAQ, though, is
a patch to the source code.

What do people think? Is a source code patch an acceptable workaround
for the 1.0 release to end users? Or should the patch become part of
the 1.0 product, in spite of the ugly #ifdef and the
duct-tape-and-baling-wire solution it contains?

Personally, I'd prefer to see the official 1.0 release do "the best it
can" with this issue, rather than sticking the poor end users with an
"Oh, you can patch your source and rebuild the product" workaround. Is
that likely without an official issue filed?

Steve Dwire

-----Original Message-----
From: kfogel@collab.net [mailto:kfogel@collab.net]
Sent: Monday, October 20, 2003 12:15 PM
To: Steve Dwire
Cc: dev@subversion.tigris.org
Subject: Re: Windows XP "Access denied" svn_io_rename

"Steve Dwire" <sdwire@pcsigroup.com> writes:
> I was looking in IssueTracker, and I couldn't find an issue for this
> 'access denied' problem. It looks like there's been quite a bit of
> discussion around it, and that it has something to do with Windows
> "file-watcher" processes grabbing hold of a file in between subversion
> steps.
> This seems to be a rather significant issue that could affect adoption
> of subversion on Windows. Is it in the issue tracker somewhere? Should
> it be?

Is it mentioned in the FAQ?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 20 20:18:39 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.