[cvsnt] Branch or Import ?

Bo Berglund Bo.Berglund at system3r.se
Wed May 12 09:20:20 BST 2004


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.


Make a branch where you are right now before you dive into the OOP version.
Then just continue on TRUNK with whatever you need to do.
If after some time you find that it was a dead end you can always go back
to the branch where the original project ended and restart from there.

Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of guastatore
Sent: den 12 maj 2004 10:22
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Branch or Import ?


Hi all,

I'm developing a prototype of an application. Now I'm considering to
re-write entire application using OOP but I have many starting points
in prototype.
So my question is: it is better splitting a branch and develop from
there considering that, probably, I will not ever have the need to
merge the branch in the trunk or it is better to copy directory
structure and import a new module into repository ?

Thanks
Antonio
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs



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