It is a client-side configurable option, which is why Versions
wouldn't know to use _svn instead. TortoiseSVN can be configured to
use either, but it is system-wide, not working-copy specific.
I'd vote for this feature to be added as a simple preference setting
in Versions for the exact reason
We have some old clients that are using projects built in Visual
Studio 2002, and it has some kind of problem with the .svn folder, so
we switched to _svn. Even though it is set from the SVN server,
Versions was still creating the folder as .svn rather than _svn.
For the time being, I am using
Glad to hear there's at least a good reason for making the
attempt. :-) I wasn't aware that one could set the folder name on
the server. IIRC, though, the .svn (or _svn) folders don't actually
exist in the repository, only in the working copy. I believe that
Versions uses the same
You would need to do this within svn itself, and I think it's unlikely that
you'd be able to configure that, as it's probably hardcoded into it. svn is
opensource though, so you could probably roll your own version...
-Ray
--~--~-~--~~~---~--~~
You received this
The first question that comes to mind is Why?, as in What do you
hope to accomplish by doing so? Do you just want them to be visible,
or is there a more involved goal? Personally, I find it refreshing
that the .svn is invisible—I shudder when working with cvs and
seeing CVS directories
