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

Re: Subversion vs. non-writable dirs

From: Romain Francoise <romain_at_orebokech.com>
Date: 2006-11-20 23:20:48 CET

Tim Hill <drtimhill@comcast.net> writes:

> Well, as you note, Subversion needs to create the .svn directory
> inside each directory in a working copy, so in this case you really
> need rw access.

Sorry if I have been unclear; I don't expect Subversion to succeed here.
I'm aware that having write permission is a hard requirement when
putting stuff under Subversion's control.

However, I would like Subversion to handle this situation gracefully.
It should certainly not just wipe the admin directory on 'svn revert' as
in my first scenario, and it should definitely not wedge the working
copy as in the second scenario.

My naive approach to the problem is that Subversion could first check if
it *can* put the 'bad' directory under version control, and *then* add
it to the entries file...

Thanks,

-- 
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 20 23:22:08 2006

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

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