| > It's kind like a snapshot-based local history. You can extend it to remote-history too, because git makes it almost trivial to create a repo that you want to work over the network (without a running server of any kind). I use git as a fancy rsync sometimes. I do most of my work on a remote box, but I still like to edit locally in an IDE, but occasionally I make a change on the remote side. On the remote side, I do git init --bare project.git git remote add clusterx remotebox:dev/project.git Then do a git clone on the remote box from that repo, then I can push changes back to that local repo and when I'm done with the day, I can just pull it all back to my laptop with a git pull. This used to be full of patch + diff + rsync in the past, but when you build stuff remotely and do diffs, but add new files to the codebase, it is so much easier to just use git. For my personal projects, I think CSS files are the most common things I've edited in this sort of loop - my web-app folders are generally just git clone --depth 1, which also takes care of the other loop where I edit locally and deploy to remote. |