Re: Unreferenced pristines behavior in 1.7

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?

----------
Joshua
Received on 2011-11-29 21:58:04 CET