[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: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 29 Nov 2011 16:17:36 -0500

On Tue, Nov 29, 2011 at 3:57 PM, Joshua McKinnon <jmmckinnon_at_gmail.com> wrote:
> On Tue, Nov 29, 2011 at 3:06 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>> Note that the difference is that now your pristines are shared.  So if
>> you have files in your working copy that are identical there is only a
>> single pristine.  Imagine a checkout of an entire repository,
>> including tags and branches.  For all of those files in your tags and
>> branches that would are just duplicates of each other there is only a
>> single pristine version stored now where as before every file had a
>> pristine.
> Oh the new working copy format is absolutely great. The point is only
> that the pristine files appear to build up over time, which seems new.
> Any extra build up is removed with an svn cleanup, but I think a lot of
> people (like me) will not realize they need to perform that step
> regularly.
> 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. When using SSDs, disk usage matters.
>> I could not find any issue # for this either.
> If no one else replies within a few days, should I create an issue to
> track this?

I filed an issue and updated the release notes:


Mark Phippard
Received on 2011-11-29 22:18:10 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.