On Mon, Sep 15, 2008 at 5:07 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Greg Stein wrote on Mon, 15 Sep 2008 at 04:29 -0700:
>> 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
>
> And what if, rather than blasted away, the WC was renamed or duplicated
> (causing the reference count to be lower than actuality)? How do you
> fix the reference counts then?
If it is renamed, then you've just "lost" your metadata. The metadata
is tied to an absolute path.
It seems possible to have some admin command to notify svn that you
renamed the directory, but I'd rather just say "don't do that, or keep
the metadata inside the WC if you're gonna move it around." Same thing
goes for copies.
>> Well, the metadata *will* know where all the working copies are.
>
> We could have the wc record itself every time some svn command accesses
> it -- is this what you plan?
I was thinking each time you did a checkout, that it would say "hey!
new working copy" and record it. There isn't a way to auto-discover a
working copy when a command is invoked because there is nothing *in*
the directory to say where it came from, what version is represented,
etc.
Cheers,
-g
---------------------------------------------------------------------
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 14:17:52 CEST