Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
My best recommendation would be to branch the trunk at the HEAD for the developer, and then revert the changes on the trunk to the last known good revision. I've had to do that for development here before, and though the branch is at an odd point in the source commits, what really matters is maintaining the history of our tags and release. You may have other reasons for trying to move the whole tree, but it's difficult for me to justify the extra work involved. Boyd -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund Sent: Friday, September 05, 2003 2:51 AM To: CVS-NT Mailing list (E-mail) Subject: [cvsnt] How to *move* a trunk section to a branch? Hi all, I have a small problem that I don't know how to handle in the best way... There is a module containing a component that we use all the time in many different products. It reached a "stable" level and all was fine. Then entered one developer with special needs and he modified the component, making it multithreaded and with all kinds of bells and whistles. In the process he managed to introduce stuff that made it misbehave *sometimes* in our regular use. Of course he did all of this on TRUNK to make it even worse, that is how it eventually was discovered. Now, what I want to do is create a branch where he started his "improvements" and move all of the following edits out on this branch so that the HEAD will again point to the stable version we had before his changes. I know I can promote the stable version to become HEAD again but at a different revision level, but this is not what I want, because the changes he made was for a reason and should be kept for him. But I want everyone that checks out the component to get tghe stable version unless they specify the threaded version. So is there a way to move file revisions on TRUNK out to a branch by some administrative commands or such? TIA Bo _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook