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

Re: Unreferenced pristines behavior in 1.7

From: Joshua McKinnon <jmmckinnon_at_gmail.com>
Date: Wed, 30 Nov 2011 11:55:55 -0500

On Tue, Nov 29, 2011 at 4:06 PM, Andreas Krey <a.krey_at_gmx.de> wrote:
> They do. For every changed file that comes to exist in the sandbox
> a new pristine copy will be lying around; after committing twenty versions
> of a file you have nineteen unreferenced pristines there.
> ...
>> I am actually in the process of doing an all-branches checkout right
>> now, to try and take advantage of the consolidation available in the
>> new working copy format.
> Unfortunately the consolidation only affects the pristines; you still
> have separate copies of identicat files in the working copy.

Thanks for clarifying how the pristine copies work. Regarding the
working copy checkout savings, yes indeed on it only consolidating the
pristine area. In my case that alone is worthwhile savings. It may take
some experimenting to find the right mix of # of branches per checkout
for savings. (I don't need ALL branches, but was curious to see it on
a large sample size)

Also, thank you Mark for updating the release notes & creating the

Received on 2011-11-30 17:56:29 CET

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.