On Wed, Nov 30, 2011 at 9:45 AM, Gleason, Todd wrote:
>
> Something similar occurred to me some time ago. It seems problematic that a
> user might move or copy WCs outside the root location though; Subversion
> would have no easy way to track that and might end up needing to re-fetch all
> the
On Tue, Nov 29, 2011 at 4:06 PM, Andreas Krey 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
> -Original Message-
> From: Mark Phippard [mailto:markp...@gmail.com]
> Sent: Tuesday, November 29, 2011 5:14 PM
> To: Talden
> Cc: Joshua McKinnon; users@subversion.apache.org
> Subject: Re: Unreferenced pristines behavior in 1.7
>
> On Tue, Nov 29, 2011 a
On Tue, Nov 29, 2011 at 6:28 PM, Talden wrote:
> 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
> 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
On Tue, Nov 29, 2011 at 3:57 PM, Joshua McKinnon wrote:
> On Tue, Nov 29, 2011 at 3:06 PM, Mark Phippard 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 checko
On Tue, 29 Nov 2011 15:57:28 +, Joshua McKinnon wrote:
...
> 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.
They do. For every changed file that comes to exist in the sandbox
a new pristine copy wil
On Tue, Nov 29, 2011 at 3:06 PM, Mark Phippard 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. Fo
On Tue, Nov 29, 2011 at 3:00 PM, Joshua McKinnon wrote:
> Having it happen automatically instead of needing to regularly run
> "svn cleanup" is definitely preferable. I've never had to run it in
> the past except in the event of a problem. (e.g. a command did not
> complete properly, or something
Can anyone comment on the state of unreferenced items not being deleted
in the pristine area in 1.7? The release notes state there are plans to
purge unreferenced items automatically, but the issue link appears to
be a placeholder (excerpt from 1.7 release notes) :
Note: In 1.7, we recommend to r
10 matches
Mail list logo
