As far as CVS goes, you can create a tag on an initial import, so for instance I have a tag called valve_2005_02_17 which was the first real Valve SDK. (Holy cow almost at the two year anniversery already!)
So the following command gives the diff between that SDK and my mod as it exists right now: cvs diff -uN -rvalve_2005_02_17 The problem is that Valve has added a large amount of brand new files since then, and all those files would now show up, which might violate the request to not have large parts of the SDK available publicly. At 2007/02/03 02:00 AM, Nikolaos Tzimoulis wrote: >What do you mean "so that it is all modified", Nate? And now that I >think about it, it's not an option to start from a specific version of >the SDK and diff that. How would everyone coordinate with that since >you don't get to choose which version of the SDK Steam downloads? >Also, it wouldn't be in accordance to Valve's policy of not having >large portions of their code public. I don't see a way of not having >to redo the patches every time an update comes out for the SDK. > >If the code management utility (like CVS) saves projects in a diff >way, then I guess that would be a viable option. The online project >could consist of CVS project files, and if one were to apply it to the >latest SDK he would get the mod's code. Is that possible? > >Nicholas > > > >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, please >visit: >http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
