[MamaSpoldi]

Originally Posted by virtuald

Yeah, disconnected operations as you describe sounds really annoying and is exactly why we don't use SVN. Here's our workflow at competitions:

• I create a bare git repo on a flash drive (cd /path/to/drive; git init --bare NAME)
• We set up remotes on each students computer to push to the flash drive (git remote add usb /path/to/drive/NAME)
• They do their normal development stuff, commits, branches, stash, etc
• When one of them wants to push code, they plug in the flash drive and do "git push usb BRANCH"
• When someone wants to pull from the flash drive, they do "git pull usb BRANCH"
• At the end of the day, I bring the flash drive home and push the commits up to git -- it's great, keeps history, no folders to keep track of -- and if someone screws something up, a 'git reset --hard HASH' allows us to go back to a known working state

Sure, git has a learning curve. But its advantages are numerous -- particularly in a disconnected environment.

The advantage of our operations at competition (the "disconnected" operations as you describe them) is that I can view the files on any computer... and we have an automatic backup if something should happen to our programming laptop. This gives us the ability to quickly recreate our environment and software on another system if it becomes necessary. And I don't need specialized tools to access the files. Sorry, I'm old-fashioned and I don't really trust the cloud as my sole backup.