That's a good point. I was thinking that it wouldn't be a big deal...
svn can easily track the references. But I guess not so much if you
just blast the WC out from under it :-P
Well, the metadata *will* know where all the working copies are. So it
would seem that "svn cleanup" can do a verification pass and re-tally
the reference counts (and do garbage collection), ensure the metadata
about the working copies is still proper, etc.
I'll add a note about it. Thanks!
Cheers,
-g
On Mon, Sep 15, 2008 at 3:36 AM, Mattias Engdegård <mattias_at_virtutech.se> wrote:
> "Greg Stein" <gstein_at_gmail.com> writes:
>
>>Note that if people keep the /bases/ directory in their home dir, then
>>the bases will be shared across ALL working copies.
>
> I may have overlooked something obvious, but how would garbage
> collection in a shared text-base tree work? Attempting to keep track
> of all WCs using it is probably fragile, so I suppose the shared
> /bases/ would just keep growing - or is there an aging mechanism that
> throws out base files that haven't been used for a while when the tree
> reaches a certain size? The client must then be prepared to re-create
> any base file that turns out to be missing. (Annoying, if working
> off-line.)
>
> With non-shared bases trees (one per WC), a single rm -rf will remove
> the whole WC and nothing but the WC.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-15 13:29:37 CEST