Re: Branching with missing revisions

The way I understood it, I was copying my WC to the branch, not copying
whatever was on the server at the revision of my current folder.

I find it kind of odd that I can make some changes, commit them, then
copy my WC to a new branch on the server and have the copied files be
an older revision.

Thanks for the clarification. I'll make sure to always do an svn update
before trying to create a new branch, even if my WC is up-to-date (and
by up-to-date I mean all files are at at least their last committed
revision)

On Aug 11, 2004, at 1:15 PM, Ben Collins-Sussman wrote:

> If your WC is at 205, and you do a commit which creates r208, your
> working copy is NOT all at 208!
>
> You have a *mixed* revision working copy. Your entire working copy is
> still at 205, and *only* those things just committed are at 208.
>
> So when you did the 'svn cp . URL', you did copy an r205 tree to the
> server. Almost entirely.

-- 
Kevin Ballard
kevin@sb.org
http://www.tildesoft.com
http://kevin.sb.org