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

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

If all goes well (Subversion takes off), a lot of ASP.NET users will start
using Subversion. They will get into trouble.

>We had a report earlier about problems with using VS.NET developing
>WebApps.
>The thing wants to mount a network share and then do 'stuff'. The 'stuff'
>includes doing some magic apparently tripping over the .svn directory,
>leading to an error message.
>
>Sounds like a general case of VS.NET needing a fix IMHO.

OK.. So the File Explorer needs a fix. And VS.NET needs a fix.

Hey, wait... perhaps svn on windows needs a fix? Cus' I don't think M$ is
going to issue a patch for this any time soon ;-)

>That's a shame and just plain broken. I'm kind of having a hard time
>believing this to be honest.

I'm not a liar, to be honest. But granted, since I haven't tested all the IO
functions in .NET, it may not be a real problem. The one that hit me was
recursive deletion using some standard stuff in the system.io namespace
(.net fw 1.1.)

> > "wc.svn" for instance? For migration purposes, both .svn and wc.svn
>could be
> > supported for a while.
>
>-1 to wc.svn or any other name that ends up in the middle of a sorted
>directory listing.

"_svn", then, as another guy suggested.

> > Please, fix this before it's to late. PRI 1 in my head.
>
>Maybe when we get more reports...

Damn it :-)

_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today!
http://www.msn.co.uk/messenger

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