Lars Kruse <lists@sumpfralle.de> writes:
> For now the svn CLI guesses, that any directory name ending in some magic
> strings (in this case: ".svn" or "_svn") must be a mistake of the user - thus
> just skipping step (1).
Wait -- does it really do that? Does it disallow any directory
*ending* in the magic strings? I thought it only disallowed any
object whose name actually *is* the magic string, and that we were
just discussing what the set of magic strings should be.
Which is it?
> yes - my naming convention ("_svn") for local copies is rare, but it took me
> some time and energy to find the cause of my problem, since I trusted in the
> reliability of the svn client. Thus I could not imagine, that the following two
> lines could make a difference:
> svn up SOMEDIR
> (cd SOMEDIR; svn up)
> (the latter always works - the first breaks for the mentioned special strings)
Yes, I understand your frustration.
There are some good reasons why we might want to block "_svn" by
default, but perhaps we should at least make this a configurable
behavior. Or perhaps we should turn it off and instead ship a
pre-commit hook that lets admins block objects named "_svn" if they
want to. I'm not sure... but first I'd like to get clarification on
my question above! :-)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 16 23:23:22 2007