Thunderbrd
C2C War Dog
This is post #3313. If you would, please link to it on the first post so I don't have to go searching for over an hour to find it againWe are used to SVN in general so we might want to use some of the more advanced features.
If you want to work on a feature that is incomplete now but should be backed up or you want others to work with you on it, you should consider making a branch.
A branch is cheap copy of the trunk that you can then change without affecting others. After you create a branch, you can switch a local working copy to it and then work with it as you would with the normal SVN. When your feature is complete, you can reintegrate the branch into the trunk and all the changes you have made will be applied. If you regularly merge trunk changes into your branch you can also stay up to date with the changes others make.
Possible uses are:
DHs barbarian diplomacy
Extensive tech tree changes that are not actually filled with content yet
Any experimental project
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-branchtag.html
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-merge.html

@Koshling: I've made some extensive changes and for numerous potential reasons, what I've done has caused savegame incompatibility. I figured it'd be easiest to ask where I went wrong by simply creating a branch (located in the branches folder under the name: saveincompat) and asking you to take a look at CvUnit, CvPlayer, enums.h, and infos files to see what I did wrong (I have a feeling you'll spot it as soon as you see the changes since the rules as to what we can and can't do are more clear for you.) I suspect its something I didn't do correctly in CvUnit wrappers.
Tomorrow, I'll be testing a few things to see if I can figure out my mistake. Half of my purpose for doing this is that I've been needing to figure out how to work with branches anyhow.