I did not know that you could run out of Q/A votes :) Makes sense though
@SteveRobillard I agree. Now that I have read about how the system works and understand it better I realize I shouldn't have been doing that. I'll delete the ones of mine that haven't been responded to.
@StevenLu and I were starting to discuss raspberrypi.stackexchange.com/q/311/141 in comments, but it would be better here on chat, so I suggested it be moved here.
@StevenLu initially responded to my +19 comment "For code, you may also want to consider using distributed version control software like git or hg, that way you not only have copies of your code in multiple places, but also have the complete history of how that code has changed." with "@MarkBooth "May want to consider" is putting it rather lightly, isn't it now? "
I replied with "Learning how to use a DVCS is a significant investment in time @StevenLu, so while you or I know it will pay off in the end for us, for some people just taking a backup may be enough."
@StevenLu followed up with "@MarkBooth I don't see why a DVCS is needed over a VCS if we are just considering being able to retrieve code later. Heck, it's even easier since you use revision numbers not commit hashes to identify a particular state. Learning a CVCS like Subversion isn't much of a time investment (as I recall... though it was a very, very long time ago). Yes, switching to Git was a bit unnerving at the time, but I have never ever looked back."
@SteveRobillard - I'm just copying them here for reference, as the starting point for a discussion. I've already deleted my reply, as it serves no purpose wrt the question. If I could remember how to create a new chapt room populated with existing comments I would have done that rather than bringing them here.
@MarkBooth bringing them here was fine and should be done when the comment thread has gotten long or wondered from the topic of the question. You did exactly what you should have
@StevenLu The point of the original question was asking how to back up the code being written. In that respect, committing the code to version control and backing it up by pushing (to github, a git server or just a bare git repo on a shared network drive) or just committing (to a remote svn server) is much the same.
I would appreciate you removing those comments and remebering that the first rule of the community is to be nice.
I understand that you are invested in the site and only want to help us toward graduation. However, The best way to do that is by maintaining a helpful and welcoming community.
@StevenLu Using a DVCS in a CVCS workflow is no more complex than using a CVCS. In fact you can use Mercurial almost exactly like you would use SVN while getting all of the benefits of a DVCS too, and running your own mercurial server can be as simple as hg serve on a private network. So backing up a complete hg repo can be as simple as running hg serve on the RasPi and then doing an hg pull on some other machine on the network.
Ideally people should vote up all answers they find useful (and vice versa) and accept the best correct answer after answers have stopped coming in. It often takes people some time to see this behaviour and start to follow that advice themselves though, and some people never get into the habbit.