[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:mime-type and detecting mergeability

From: <cmpilato_at_collab.net>
Date: 2002-08-22 19:39:45 CEST

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

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.