> 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 used to work (pre 1.7) with many branches including the trunk in separate WCs Now I check out the project path with branches and tags being depth empty except for selective checkout and check out the trunk... all nicely in the same WC (and hence shared pristines) without checking everything out. The shared pristines pay off very well here. That said, an 'svn cleanup' recently recovered >200mb and nearly 25000 files so automatic pristine cleanup will be very nice when it arrives. I'd actually like the ability to separate the pristine-store from the WC root since I'd like to have several WCs for the same trunk or branch with various pieces of work-in-progress - sharing pristines there would be great. Maybe something like the Bazaar shared-repositories. Just look up the path until you hit a .svn that contains a pristine-store. .../work/ .svn/ <--- contains a pristine store, not a WC. All of the pristines of WCs below. projectX/ default/ .svn/ <-- the root for this WC trunk/ ... branches/ <-- @ depth empty - only the branches I want checked out. feature-123/ ... feature-456/ ... that-thing-i-am-doing-on-trunk/ <-- same trunk as .../work/projectX/default/trunk .svn/ <-- the root for this WC that-other-thing-i-am-doing-on-trunk/ <-- same trunk as .../work/projectX/default/trunk .svn/ <-- the root for this WC I personally think this approach is better than the suggestion of a pristine-store in your profile for the whole machine. Sometimes you do want separation. You can always link the folders off elsewhere. -- Talden