Greg Goodrich wrote:
> I've scanned through the mailing list, and may have come up with some
> similar circumstances to my question, but nonetheless, I wish to point
> out what I consider a "strange" behaviour of the svn copy command.
>
> My issues thus far are encapsulated in my efforts to convert from VSS to
> Subversion, and therefore the copy command that I'm running is
> "generated" by a script. This may or may not be useful background info.
>
> Given a repository:
>
> dev
> |
> -- tags
> |
> -- trunk
> |
> -- Charting
> |
> -- cp32
> |
> -- Notebuilder
> |
> -- Utilities
> |
> -- UserMan
>
> All "nodes" are folders in the above tree.
> If I now do the following command:
>
> svn copy --message "version" $repos/trunk/Charting
> $repos/tags/V4.4.2/Charting
>
> What I get is a V4.4.2 folder under tags, with cp32 and Notebuilder
> folders under V4.4.2. This seems strange, but not necessarily incorrect.
>
> Now, if I run basically the SAME command, with a different source
> "folder":
>
> svn copy --message "version" $repos/trunk/Utilities
> $repos/tags/V4.4.2/Utilities

Please could you post an actual copy/paste from a terminal window, and
corresponding pieces of "svn log -v" ourput.

I ask this, because the command lines you quote simply don't agree with the
behaviour you describe.

Is it possible that the final "Charting" and "Utilities" were missed off the
actual executed copy-destinations? Because that would explain what you
describe.