[cvsnt] Betr.: CVSNT to CVS

Tony Hoyle tony.hoyle at march-hare.com
Wed Apr 8 13:58:14 BST 2009

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.

Andreas Krey wrote:
> ...and get the flames when the next merge fails because of the
> mergeinfo that wasn't created because he carried over the files
> by hand.

Depends if the directories are ever intended to be mergable.  If they're 
not, then both options are equivalent.

> On the other hand 'svn copy' basically only exists to create tags
> and branches anyway. Who ever needs two directories that are
> mergeable to each other within a project tree?

It happens.

eg. customer specific modules, one per directory.  You'd copy those to 
keep them mergable and make the customer specific changes - if the base 
module changes you merge from one to the other.

svn suports this.  cvsnt could check that out but couldn't create the 
copies, or do the merges.  IIRC tfs could do it as well.


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook