Re: ".svn" directory name no good (in fact, it is worse than I thought)

This would advocate the need for having the setup configurable.

Question is, does it make it enough of an issue to need to have it configurable now?

Here's the problem.

I have a samba fs, on a *nix box attached to a Windoze machine.

I *still* can't create a .svn directory on that machine.

So what would I do under windoze to handle that???

Personally, I would advocate AGAINST having a working copy mounted across
heterogenous environments, especially taking into account the whole CRLF issue.

What do you think? Is this point mott then??? The heterogenous mounting issue?

I think the OS under which subversion is being run as the client should govern where
the working directory goes.

Shamim Islam
BA BS

Roland Bramm (roland@butlers-djihad.de) wrote:
>
>>
>>How about this amendment to idea 2: as soon as the subversion client
>>encounters a .svn directory in an working copy on a windows platform, it
>>automatically converts it to _svn. Same thing the other way around for every
>>other operating system, and working copies would still be moveable across
>>plattforms. Second advantage of this approach: Existing working copies on
>>windows would silently be converted to the new syntax (as soon as the user
>>updates its client), making a new checkout or a seperate conversion tool not
>>necessary.
>
>Think of the chaos which can appear if you mount a "unix" volume with
>Windows and use svn or the opposite way ...
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 18:40:49 2003