Quote:
|
Originally Posted by gnirts
So it seems that others are using Subversion as well. A few questions about version control in general:
Which files in the code directory does everyone put under version control? Just .c and .h? .hex too? What about documentation?
|
Generally speaking the version control systems work best with textual data rather than binary files. So, things like documentation, the .h and .c files, etc. would be good to put in. You can, of course, have binary data there too (like the .hex files, images, etc.), but, the version control systems generally won't give you features like comparing the changes from one version to another with that type of data.
Quote:
|
Originally Posted by gnirts
And how often does everyone commit? Major revisions? Every compile?
|
The general rule of thumb we use is commit after any changes that are stable enough to have passed some very basic preliminary testing (e.g. no syntax errors and such). I tend to do it more or less every time I would ordinarily save a file (less any of those where it would fail the preliminary tests).
Quote:
|
Originally Posted by gnirts
Lastly, do people using CVS/SVN use the tools inside MPLAB or Tortoise?
|
Since we're not using it for robot code (and thus not MPLAB) I can't directly answer that question. What I will mention (which may not be of particular relevance to you personally, but others reading this thread later may find useful to know) is that Eclipse (which I believe I've read from some other threads in the past can be used to program the robot, but that I use with the PHPEclipse plugin for writing PHP code) has plugins for both Subversion and CVS. I haven't used those extensively; I usually use the command line interface to CVS/Subversion (then again, I often develop these things when logged remotely into other boxes and anything else could be prohibitively slow).