[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: Ryan Schmidt <subversion-2006d_at_ryandesign.com>
Date: 2006-11-21 03:31:00 CET

On Nov 20, 2006, at 16:20, Romain Francoise wrote:

> 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.

Implementing support for opaque collections a.k.a. document bundles
in Subversion could be a solution to this problem as well.

http://subversion.tigris.org/issues/show_bug.cgi?id=707

> 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.

Agree.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 21 03:31:41 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.