One for the nerds....
So I now have 2 or 3 machines I use for tinkering with the little projects I have, and I'd like to keep the code synched. There are many tools for this, of course, and I'm not wanting to start a religious war about which tool I should use, but rather seeking advice on how to use them best :)
Assume, for the sake of argument, that I have access to git and/or subversion. Assume, for the sake of argument, that I have a ~/Code directory, which has, of course, a Python directory and a Perl directory, which then contain project directories and library directories.
Assuming for the moment that I don't care so much about synching "broken" code - in that I want to be able to half-finish something on the desktop, commit it to the repo, and check it out on the laptop to keep tinkering - as much as I care about the latest version, is my best strategy to commit ~/Code en masse and then just update en masse?
Or should I commit each project individually to the repo, so I can branch later if need be?
Assume, for the sake of argument, that I have access to git and/or subversion. Assume, for the sake of argument, that I have a ~/Code directory, which has, of course, a Python directory and a Perl directory, which then contain project directories and library directories.
Assuming for the moment that I don't care so much about synching "broken" code - in that I want to be able to half-finish something on the desktop, commit it to the repo, and check it out on the laptop to keep tinkering - as much as I care about the latest version, is my best strategy to commit ~/Code en masse and then just update en masse?
Or should I commit each project individually to the repo, so I can branch later if need be?
no subject
You want to keep directories in sync across different machines, put them inside Dropbox. There are other solutions, but I guarantee you Dropbox is the simplest, quickest, and least prone to error, by a very very long way. Just the dev directories, if you like, since presumably the stable branches shouldn't contain anything except correct stable versions.
no subject
no subject
no subject
no subject
Dropbox treats that symlink as though it were a real directory so far as the other client machines go, so anywhere I don't explicitly exclude ~/Dropbox/Music from sync, it'll just pull all the music across as a directory rather than as a symlink.
This may be useful if for some reason you really want stuff in random directories in different places but still want Dropbox to sync it all.