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

Re: Pre-Design Discussion of Server->client configuration

From: steveking <steveking_at_gmx.ch>
Date: 2005-04-29 19:11:52 CEST

John Peacock wrote:
> 3) The recursive nature of the WC means that every subtree must have
> _all_ of the information available all the time. This either means that
> things like inherited properties or server config files have to be
> stored either in the WC admin files in each and every subtree or they
> have to be stored in some common space outside of the WC tree entirely
> (like the .subversion directory). Common config files could be stored
> in a hash by UUID in the .subversion directory for caching purposes, but
> it would mean that deleting a WC would not remove this information from
> the disk (unless a new 'svn release' command were added).

Is the '.subversion' directory you mention here the one where the also
the 'config' and 'server' file is located? (%APPDATA%\Subversion on
If yes, then I think that would be the best way to go with server-side
configs. We could store them in a subfolder 'serverconfig' like e.g. the
authentication data is stored now.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 29 19:20:55 2005

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