TZF - Version control (totally off topic :) )
"B. Evers" <[email protected]> Mon, 23 Feb 2004 19:53:57 +0100
| Newsgroups | gmane.comp.lang.delphi.topaz |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_032B_01C3FA46.C631E800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, This is totally off-topic for Topaz issues, but I was just wondering :) I uesd CS-RCS before for version control. I am currently migrating to CVS (using cvsnt as a server and tortoise CVS as a client). I was wondering what you guys use as a version control strategy. With CVS you can create one repository or multiple. By putting all projects in one repository you could use components (and their versions) through all your projects (though you should check all related products when a change is made to a common part). With multiple repositories (1 per project) you can not use common components anymore (I think), but you have the advantage that you can burn the entire repository to CD and have the full history available of that project. I was just wondering what strategies (and tools) you guys use for this. Benno --^---------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?clvXPN.a5kvff.Z2NsZHQt Or send an email to: [email protected] TOPICA - Start your own email discussion group. FREE! http://www.topica.com/partner/tag02/create/index2.html --^---------------------------------------------------------------- ------=_NextPart_000_032B_01C3FA46.C631E800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2800.1400" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV>Hi,<BR></DIV> <DIV><FONT face=Arial size=2>This is totally off-topic for Topaz issues, but I was just wondering :)</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT><BR>I uesd CS-RCS before for version control. I am currently migrating to CVS<BR>(using cvsnt as a server and tortoise CVS as a client).<BR><BR>I was wondering what you guys use as a version control strategy. With CVS<BR>you can create one repository or multiple. By putting all projects in one<BR>repository you could use components (and their versions) through all your<BR>projects (though you should check all related products when a change is made<BR>to a common part).<BR><BR>With multiple repositories (1 per project) you can not use common components<BR>anymore (I think), but you have the advantage that you can burn the entire<BR>repository to CD and have the full history available of that project.<BR><BR>I was just wondering what strategies (and tools) you guys use for this.<BR><BR>Benno<BR></DIV><PRE>--^^--------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: <A HREF="http://topica.com/u/?clvXPN.a5kvff.Z2NsZHQt">http://topica.com/u/?clvXPN.a5kvff.Z2NsZHQt</A> Or send an email to: [email protected] TOPICA - Start your own email discussion group. FREE! <A HREF="http://www.topica.com/partner/tag02/create/index2.html">http://www.topica.com/partner/tag02/create/index2.html</A> --^^---------------------------------------------------------------</PRE> </BODY></HTML> ------=_NextPart_000_032B_01C3FA46.C631E800--