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

My week-old Workstation with brand-new Windows XP install works fine
with .svn as-is. You have to install buggy software on top of that to
have a problem. Visual Studio 6.0 works fine for me.

Maybe he could go into Folder Options and define an "svn" file type so
that a lookup of "*.svn" succeeds? If that doesn't work I'd wonder
just how Windows-compatible ASP.NET really is.

I wouldn't make any changes to support .NOT until someone documents
just what it can and can't handle. Otherwise you're just chasing
Microsoft bugs with success in view.

From: Ben Collins-Sussman <sussman@collab.net>
Date: 24 Sep 2003 16:34:34 -0500

> But that is really stupid, yet nothing else works properly. I assure
> you, ".svn" is going to bite a lot of Windows users.

Windows users have been happily using '.svn' for over 2 years.
There's no giant revolt about to happen. I view my '.svn' directories
in Explorer all the time.

> I see no reason why this shouldn't be changed this into something that
> works properly ASAP (given that this name is fairly localized in the
> code base)

The admin dir is #defined to '.svn', so in theory, it *could* be
user-configurable, or just different on win32. But we had this
discussion years ago, and wanted people to converge on a single
interoperable standard.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 05:58:37 2003