Well in core we never developed "trunk" on a "branch" :) But essentially I moved everything by hand; every branch, every tag, etc.
You are not going to be able to maintain history in both place as far as I know. I think the closest you would get would be to: 1) svn mv https://svn.jboss.org/repos/hibernate/branches/Branch_3_2/HibernateExt/tools/ https://svn.jboss.org/repos/hibernate/tools/trunk 2) svn cp https://svn.jboss.org/repos/hibernate/tools/trunk https://svn.jboss.org/repos/hibernate/tools/branches/Branch_3_2 On Fri, 2010-07-09 at 14:28 +0200, Andersen Max wrote: > Hi, > > I know this is a long overdue, but i'm now creating > > https://svn.jboss.org/repos/hibernate/tools/ > > and is trying to figure out how to make what were done in > https://svn.jboss.org/repos/hibernate/branches/Branch_3_2/HibernateExt/tools/ > the new trunk (maintaing history etc.) > > Is svn mv the only option ? (not liking that much since it removes the branch > too..) > > svn cp would give me the exact copy but not retain the revision info afaik. > > Anyone remembers how it were done back in 2007 for core and the other modules > ? > (svn history seem to indicate svn mv were used, but that were fine then > because the branches and trunks were copied to corresponding branches and > trunks) > > /max > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Steve Ebersole <st...@hibernate.org> http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
