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

Re: does svn support one 'Centralized Metadata Storage' across diffent working copies ?

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 8 May 2012 00:28:25 +0300

Stefan Sperling wrote on Mon, May 07, 2012 at 18:12:30 +0200:
> On Mon, May 07, 2012 at 11:51:44AM -0400, Bob Archer wrote:
> > It sounds like what he is asking for more than a "shared working copy metadata" is sharing the pristine. For example, if I have a file that is in 10 branches and they all have the same pristine it will use that one pristine rather than a pristine for each copy in each branch. Perhaps that is what you mean when you say "shared meta-data" but that wasn't my understanding of this.
> >
> > Frankly, for me, working copy disk usage is the least of my concerns.
>
> Pristines are a subset of the meta-data, so shared metadata implies shared
> pristines.
>
> Note that you can share pristines between branches today by using a single
> working copy for all branches you work on. Check out the repository root
> with the "--depth empty" option and then pull in the branches you need
> via "update --set-depth=infinity".

'update --parents' and 'update --set-depth=immediates' might be useful
too, to pull in the intermediate dirs (those 'above' a branch root).

> See http://svnbook.red-bean.com/en/1.7/svn.advanced.sparsedirs.html
>
> Note that with Subversion 1.7 this will only reduce disk space, not network
> traffic. Preventing Subversion from downloading the same pristine multiple
> times is currently being worked on. That feature should be available in 1.8.
Received on 2012-05-07 23:29:14 CEST

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

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