Hi Robert, Ben, James & Martin, thanks for your responses. I've followed the links supplied and read your comments carefully. It seems that we really need to introduce tagging to set defined versions we can go back to to solve our problems.
Currently we have a 'trunk' and a 'branch' for each of our projects. We work off the branch and in most cases immediately merge with the trunk once the work on the branch is complete. If I understand correctly it might be worth reconsidering this. Before we make changes which are not additions or fixes but change our code structurally we should create a new tag. I still have to learn more about SVN with respect to selectively checking out code (I don't need the full code base for each branch) and retagging. Thanks for your help! Cheers, Jens The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax does not accept legal responsibility for the contents of this message or attached files. ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
