Shameless self-promotion (to complement the Perforce article advertised by Jay):
http://developer.valvesoftware.com/wiki/User:RavuAlHemio/Tackling_SDK_updates_with_Subversion By the way, Subversion and (AFAIK) CVS also use "branch" terminology. ~~ Ondra On 10.06.08 23:57 Uhr, Chris Green wrote: > The best way depends on what version control software you are using. > Using perforce terminology, basically what you want to do is have a > branch in your version control system which represents the unmodified > sdk code. You start your project by checking in the unmodified code and > then branching your project off of that. When you get a new drop from > valve, check that code into the valve branch and integrate it into your > project. That will perform the merge in a "smart" fashion. Cvs, > subversion, etc will use similar methods. > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
