[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 21:41:17 +0200

On Mon, Sep 15, 2008 at 10:21:46PM +0300, Daniel Shahaf wrote:
> Stefan Sperling wrote on Mon, 15 Sep 2008 at 21:06 +0200:
> > The only problem I'm seeing here is that needing access to
> > another working copy to determine whether the current working
> > copy is a copy is quite fragile. The other working copy
> > may be on a drive that's unmounted or horribly slow... :-/
> >
> We don't need access to the other working copy -- we can store both its
> path and its wcuuid in the centralised store.

Oh, good point :)

> > Hmmm... so maybe requiring user interaction to sync working
> > copies with the central meta data store is indeed the way to go?
> > I don't like this, but I acknowledge that automatically managing
> > moved/copied working copies may be non-trivial to implement.
> >
> Agreed, I conjecture we'll want manual control anyway (even if some sort
> of magic wcuuid system is used). With all of us (except Greg :)) moving
> and rsyncing wc's all the time, keeping track of it might not be easy.

Yes, of course, a manual system is needed. It was not my intention
to imply that it wouldn't be needed.

But if we can handle some of this stuff automatically, why not?

> I don't view this as an extension to 'svn mv/cp', though -- I consider
> a separate command that just tells svn "Here is a wc, add it" or "Here
> was a wc, forget it". That's so I can use tar or rsync or ... to move
> or duplicate my wc's.

Let's just have the manual way first and try to introduce some
form of automatic working copy tracking later. Having the concept
of unique IDs for working copies would probably be a nice feature
in any case.


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 21:41:41 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.