Ben Collins-Sussman <sussman@collab.net> writes:
> > 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."
We could always go with a configuration option for allowable
additional names for admin dirs. That is, make the client code expect
.svn (as in, *always* try that first), and failing that, try the
ordered list of names in that config option.
This means you pay no penalty for continuing to use .svn (and by the
way, we still would never allow you to version a path named ".svn",
regardless of your current WC admin name). Folks who want to use
something else will pay the try-fail-try-again cost, but, well, that's
just tough.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 07:12:39 2003