Re: Branching with missing revisions

The changes from revision 205 to revision 208 were ones I personally
made to my WC and committed, so I know it was up to date.

The only thing I can think of is if my WC folder was marked as revision
205 (i.e. if I had a mixed-revision WC where each file was at it's last
committed revision rather than HEAD) and the copy decided that since
the copied folder was marked as revision 205 it would copy revision 205
on the server to the new branch. Is that possible?

And when you say a transcript, I'm not sure what you want. A log of
what I saw certainly wouldn't show any more information than what I
said here.

Oh, and in case it matters, the server was v1.1.0 (don't know what
build, it's not my server).

On Aug 11, 2004, at 8:51 AM, Ben Collins-Sussman wrote:

> Can't explain it. If your working copy was all at r208, then the copy
> action should have created a branch with r208 contents, not r205
> contents. Are you *sure* your working copy was all at r208?
>
> In any case, the important thing here is to try and reproduce. We
> need to see a transcript of this bug happening.

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