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

Re: directory named "_svn" is ignored

From: Lars Kruse <lists_at_sumpfralle.de>
Date: 2007-11-12 20:48:55 CET


> Lars, I believe that we specifically disallow "_svn" in the repository
> for interoperability between different clients that are using both
> ".svn" and "_svn" administrative directories. If we allowed "_svn"
> into the repository, how would the users who have SVN_ASP_DOT_NET_HACK
> pull that directory from the repository?

Maybe I overlooked something, but from my point of view, the following thing
should happen after issueing "svn up SOME_DIR":

 1) check if SOME_DIR contains a subdirectory called ".svn" resp. "_svn"

 2a) if (1) succeeded, then SOME_DIR is a valid directory

 2b) if (1) fails, then check if the last part of SOME_DIR is ".svn" or "_svn" -
in this case, obviously the user wanted to ask for the parent directory of
SOME_DIR (e.g. issuing "svn up foo/.svn" instead of "svn up foo")

If I don't get it wrong, then the current behaviour is:
 start with (2)
 continue with (1)
The opposite order should be correct, I would say.

In my case, the directory called "_svn" is the root directory of my local
working copy - thus there is no conflict here.

I do not see a scenario, where a reversed order of checks (as described above)
could cause a conflict with the SVN_ASP_DOT_NET_HACK.
Or am I missing something?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 12 20:50:04 2007

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.