[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Base text files, re: IRC chat

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 15 Sep 2008 14:41:47 +0200

On Mon, Sep 15, 2008 at 05:17:25AM -0700, Greg Stein wrote:
> 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.

Couldn't we also track this the other way round?
As in, have the working copy know where the meta data is located?

I guess the next question would be where to put meta data about
meta data :) I'd suggest a mandatory .svn directory at the WC root.

> 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.

Please let's not just punt on this. Working copies may get renamed/moved
for any number of reasons, sometimes beyond control of individual developers.

E.g. network shares that are mounted at different paths on different
systems -- I know that is a stupid setup but in reality this kind of
stuff exists in the wild, and it would be probably a PITA for many
people if Subversion wasn't able to work in such environments.

I'd rather assume that working copies get moved around all the time
(in their entirety) than assume that they never will.
> >> 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.

We could _always_ have a .svn directory at the WC root, right?
And if this directory does not host the meta data itself, it could
provide a pointer to where it thinks the meta data should be.


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:42:03 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.