4 ms·

Isn't git or mercurial more appropriate for archiving programming projects?

• Nullabillity 9y ago
  For archival, yes. But it's not rare that I want to swap computer without committing WIP changes.
  • parthdesai 9y ago
    Wouldn't a branching do the trick? checkout a WIP branch and push it. You can pull it on any other computer you want, keep working on it till you are comfortable enough to merge back on master/develop.
    • whatever_dude 9y ago
      While that sort of works and I do that, it's a much more cumbersome solution. I commit WIP code to a separate branch, change, and now if I go back to the original computer, I need to make sure to push, go back, pull again... god forbid I had done interactive rebasing or amended a commit, since it'll be all of of sync... it's just more more complicated than simply saving a file and having it reflected. "Temporary commits" should be a rare thing, not mandatory. I end up using both git and dropbox for some projects and it mostly works, but having projects on dropbox is a mess because of node_modules, having sync running continuously because some tools/projects/IDEs will keep generating temporary files, etc.
      • parthdesai 9y ago
        Oh i do agree, it's cumbersome and dropbox should have .dropboxignore file. I was just suggesting a work around :)