Hi,
> 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?
ah - good question - now we can clear up the confusion:
for now I was always talking about the top directory of my local working copy.
Thus this is not a name of an item within the repository, but just the name of
a directory within my local filesystem.
Then I did some more tests and now the problem seems to be clear:
(1) svn mkdir _svn
output: svn: Not enough arguments provided; try 'svn help' for more info
(2) svn up SOMEDIR/_svn
result: svn always tries to update the _current_ directory - no matter, what
SOMEDIR contains
(3) svn co https://systemausfall.org/svn/lars _svn
result: a local directory named "lars" is created, instead of "_svn"
It looks like svn simply ignores any command line argument ending in ".svn" or
"_svn", since all of the above examples show the behaviour, that would happen
_without_ the specific argument.
So my previous assumption, that the svn CLI removes the last part of a
directory if it is ".svn" or "_svn" was wrong.
Instead, it completely ignores all the arguments that happen to end in one of
these magic strings.
I hope, this helps to clarify the problem,
Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 17 05:09:04 2007