I *could* set up svn for code management but I'm the only developer and I decided to do something different just for the hell of it. It works for me so why not.
When I have a working version and I'm ready to move onto the next coding stage, I rsync it to my Snow Leopard machine, go to the Time Machine icon on the menu bar and hit 'Backup Now'. Then if I want to go back, I can just get the old stuff out the Time Machine.
Doesn't give me the fill gamut of what svn gives but it works for a small project like this.
Other related posts:
Google Desktop for Mac breaks mdimport/Spotlight
Now I know why I prefer BSD
Comment by James, on 13-Feb-2010 12:47
Seems like a pretty hodge-podge system. You should look at something like mercurial, one of these days I'm going to get around to replacing my very spread-out subversion repository (website development so each site gets it's own active branch) with mercurial.
Comment by Ralph Corderoy, on 14-Feb-2010 04:08
One of Mercurial's main competitors is also Python; Bazaar, backed by Canonical and used heavily in producing Ubuntu. http://bazaar.canonical.com/en/ Bell Labs used to do something similar during their development of Plan 9. Their filesystem would be snapshotted once a day, novel at the time, and they'd often diff two days' source trees to see what had changed. http://en.wikipedia.org/wiki/Fossil_%28file_system%29
Add a comment
Please note: comments that are inappropriate or promotional in nature will be deleted.
E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.
Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments. If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.