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

"Ronald Cannes" <roncannes@hotmail.com> writes:

> 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.

> >Windows can handle it, the individual applications are the problem.
>
> Applications that *ship* with Windows cannot handle it! Try creating a
> ".svn" directory using the File Explorer. It won't work.

It's true, Explorer can't create '.svn', but it can display it just
fine. That's not a real problem.

> Also, some of the Win32 SDK functions cannot handle it, at least not
> the .NET version of those functions.

Arlid Fines (the AnkhSVN guy) has never witnessed these problems; can
you be more specific?

He says VS.NET deals with '.svn' just fine when dealing with local
projects, but doesn't know about ASP.NET web projects. Is that what
you're having problems with?

> 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.

Should we forget the standard?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 24 23:36:08 2003