kevin@pilch-bisson.net writes:
> While I agree that it might be nice to have subversion repository
> properties for doing things like this, I'm not sure how necessary it
> is.
>
> Here's another suggestion: Users can store default
> ~/.subversion/config file in their repository, check them out, and
> copy the files to their own home dirs.
>
> I.e. have a repos layout like this (for perhaps a corporate network):
>
> /
> trunk/
> branches/
> tags/
> config/
> proxies
> options
> ....
>
> Then, when a new employee starts they
> ~ $ svn co http://svn.mycompany.com/repos/config/ ~/.subversion
>
> And all is happy!
...until one of those configuration options one day conflicts with the
options needed by a different project's working copies. I have no
concrete examples, but I would like to see configuration options have
this precedence heirarchy:
- working copy (as dictated by settings on the repos)
- ~/.subversion (user default)
- /etc/subversion (system-wide default)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 19:38:59 2002