You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@galois.collab.net> on 2001/02/21 14:19:09 UTC

Re: Little question about directory copies

Greg Hudson <gh...@mit.edu> writes:
> Sorry to distract people from their fs work, but this has been bugging
> me for a while.
> 
> Suppose I'm ready to make a release branch for a very large project.
> I go to my working directory and run:
> 
> 	svn branch foo foo-1.7
> 	svi ci
> 
> (or maybe I just use "svn cp"; I don't know whether the current plan
> is to have two separate operations or not).  In the repository, after
> the commit, foo and foo-1.7 will point to the same node-revision, and
> future changes will result in all the cool copy-on-write stuff talked
> about in the structure document.
> 
> My question is, what happens in the working directory when I run the
> "svn branch" command?

I think it should switch over too, unless you explicitly request that
it not.  On this matter, imho CVS fails: I've seen so many users
become confused at CVS's default behavior, which is to *not* switch
the working copy over to the just-created branch.

However, I haven't given it much thought beyond that instinctive
reaction, as it's a user-interface decision that won't really affect
much underlying code.  So maybe there's some advantage to the CVS way
that I'm not thinking of here.

-K