You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by solo turn <so...@yahoo.com> on 2004/04/23 10:56:35 UTC
Re: solved, was: access is denied, was: permission denied
--- Branko Čibej <br...@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 ..."? it IS read only, and it was for a long
time, and it should not be? 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.
tried a fresh checkout of a part, and there the .svn are just hidden. 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 ;)
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25�
http://photos.yahoo.com/ph/print_splash
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: solved, was: access is denied, was: permission denied
Posted by Branko Cibej <br...@xbc.nu>.
Quoting solo turn <so...@yahoo.com>:
> --- Branko �ibej <br...@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*
Yep.
> 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