See, that's what I thought. What you're saying is that when I do the
copy, what's in my WC will be what's copied, which is what I expected.
My WC was mixed-revision but every revision was at least at the
last-committed revision (plus the couple of modifications in files,
which is why I was doing a copy of my WC instead of just the trunk on
the server), so what showed up in the branch should have been up to
date. Instead, what showed up in the branch was entirely revision 205.
What it looks like is doing a 'svn cp wc URL' doesn't copy my
mixed-revision WC properly, instead it copies the revision on the
server that my WC directory is marked as. But that's only conjecture.
On Aug 11, 2004, at 1:29 PM, Ben Collins-Sussman wrote:
> The other thing to clarify here is that 'svn cp wc URL' will build a
> transaction-tree on the server that is an *exact* reflection of the
> mixed revisions in your working copy. So before you run such a
> run 'svn status -v wc' to see exactly what you're copying to the
Received on Wed Aug 11 19:36:10 2004
- application/pkcs7-signature attachment: smime.p7s