3 ms·
Are there really people whose ONLY copy of a project is on GitHub? If so, I think they're not doing distributed version control correctly.
by teach 12y ago
Are there really people whose ONLY copy of a project is on GitHub? If so, I think they're not doing distributed version control correctly.
- lucaspiller 12y agoI have old projects on GitHub that I haven't touched for a few years. They are things that I don't really care about if I lost them though.
- ericlathrop 12y agoThis tool helps you stay distributed by keeping a server somewhere that constantly backs up all your repos. With this you can't accidentally forget to make a copy if you make a quick repo in a coffee shop somewhere, and delete the local copy days later when you're cleaning up.
- deanclatworthy 12y agoOr you could mirror to multiple repositories with one push. I write about how to use Github & Bitbucket simultaneously here: http://deanclatworthy.com/2013/01/how-to-avoid-relying-on-github-mirror-your-repository/ http://deanclatworthy.com/2013/01/how-to-avoid-relying-on-gi...
- ericlathrop 12y agoWow, that's a pretty neat approach! How well does that work with multiple people?
- tomswartz07 12y agoI can't imagine it would be that difficult with multiple people. Even if they pulled from one or the other, so long as someone merges the changes from the missing repo, everyone will be good to go. This is a pretty unique approach to multiple git servers.
- zeckalpha 12y agoI mirror most stuff between Bitbucket and GitHub, plus local copies of course.