I'm not sure if this is what you mean with those commands, but if in the
end what you want a single path like /trunk to show you the timeline of
releases, e.g.
trunk 1789 copy of /tags/XYZ_1.3.0_BUILD32_RELEASE_RC1
trunk 1234 copy of /tags/XYZ_1.2.0_BUILD24_RELEASE_RC1
trunk 1111 copy of /tags/XYZ_1.1.0_BUILD11_RELEASE_RC1
then I think that, apart from the name "trunk", that sounds more than
reasonable. It is much more quick, clear and robust than merging in
changes and hoping the result is the same as a copy.
I think you'd have a problem getting the listing above with tools trying
to "follow" the copy of a root folder. But I hope an additional
subdirectory would fix that. Just have a single directory called "link"
in trunk and the log of trunk should show:
trunk/link 1789 copy of /tags/XYZ_1.3.0_BUILD32_RELEASE_RC1
trunk/link 1234 copy of /tags/XYZ_1.2.0_BUILD24_RELEASE_RC1
trunk/link 1111 copy of /tags/XYZ_1.1.0_BUILD11_RELEASE_RC1
However, why you would use the name "trunk" for this? A trunk is usually
where branches grow out from, not where you stick them into!
--
Stein
