If you have ssh access to their machines, you can just set up their repo as a new remote.

If not, "git bundle" supports coordination via email, which is the workflow that git was originally designed to support.

You can at the very least send each other a zip file containing the .git directory. When you extract that directory into a separate directory, you can add it as a remote and fetch/pull from it (because that's the entire repository right there).

What I usually do is I copy the .git to another name before running zip, so it doesn't extract as .git :)

This is also one of the reasons you shouldn't commit binaries, especially large ones.

For Mercurial, you'll need to run "hg serve" to have a lightweight Mercurial server up and running, so other developers can pull from you just like from any other repository:

    hg pull -r deadbeef http://developer-01:8000/

Remember, we're in DVCS land here.

One of the the nice things about a DVCS is that you can do something like work with as many copies as you need - there's no downside to pushing a copy out to a spare server where everyone can access via SSH until the main repo is back online.

git remote set-url origin link I set a new remote which would be a server we host that is also running git, or one of our personal computers will act as the remote until Bitbucket is back up. the thing is, the service hasn't been down for long periods of time, so the normal mode of operation is to push locally until we need to push to remote, which Bitbucket usually is up.