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

Files <files@poetryunlimited.com> writes:

> Out of idle curiosity, since we all seem to be so big on CVS
> compatibility and the like, I'm surprised that we never ended up with
> SVN as the name of the admin path.

That was the original name, three years ago. Then everyone cheered we
changed it to .svn/

> Is it too late to revisit that now? Just wondering.

I think the commandline users (unix folk) really were happy when the
directory became invisible... at the moment, I'd rather go with Jack
Repenning's plan: create _svn on win32, .svn on unix, and the client
tolerates either format when reading.

> And lastly, why *isn't* the admin path configurable with a .svn default?
> How does interoperability have to do with a path component that is
> localized to a current filesystem where the library is already
> intelligent enough to know where the admin textbase is located via the
> configuration file or command line override?

It means I can't hand you my working copy. Why not? Because I just
happen to use "7ex983p" as my admin directory names. I like it.

"Oh, you want to read my working copy too? I guess you'd better
temporarily configure your client to use that same admin directory
name. You can change your configuration back later."

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 06:24:39 2003