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

Re: solved, was: access is denied, was: permission denied

From: Branko Cibej <brane_at_xbc.nu>
Date: 2004-04-23 18:56:14 CEST

Quoting solo turn <soloturn99@yahoo.com>:

> --- Branko &#65533;ibej <brane@xbc.nu> wrote:
> > And the weird thought is: something is setting the read-only bit on
> > .svn directories in that working copy.
> aehm ... what do you mean by "something is setting ..."?

Subversion doesn't make .svn directories read-only. So something else must have
done that.

> it IS read only, and it was for a long time, and it should not be?

Nope. :-)

> but i cannot remember how it became read-only.
> *arghh*


> i reset all .svn to read/write now. and it works. but an error message
> "is read only, really remove? do it for all?" would be nice ... and
> less confusing.

Since Subversion doesn't set the read-only bit on those directories, and we do
say not to touch them, an "access denied" error should be quite sufficient IMHO.
I don't think we want to do is start putting even more Windows-specific WC
handling into the code.

> tried a fresh checkout of a part, and there the .svn are just hidden.

Good. That's as it should be.

> so i'll wait and see if something becomes again read-only. otherwise
> it seems solved, thanks a lot.
> and again brain cleared a long thread with a little mail ;)

/me .oO(the winner and still champion! :-p )

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 23 18:56:37 2004

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.