问题
I see many CS students who use Dropbox as an alternative to real SC systems due to its ease of use.
Do you use Dropbox as a quick-and-dirty source control solution? Is this a valid use for it?
回答1:
Not really, but Dropbox in concert with GIT, maybe. For a single developer scenario where you want to work on more than one development machine, I think this would work just fine.
回答2:
I think as a quick and dirty approach, yes, it's fine. What everybody seems to not realise is that Dropbox does save the history of your files.
You wouldn't be able to easily go back to a previous project state though, just a previous state of individual files.
So yes, if you want VERY quick and VEEERRRRY dirty, then go for it.
回答3:
The Linux kernel was developed via patch files for a long time and it worked.
I'd say any solution that works is "valid" - whether it is recommended, good practice etc is another matter entirely. I'd point them to github, set up a git server (very easy to do) or an SVN server, personally. I'd also ask for their commit log.
回答4:
Not Source Control, maybe just a Source Backup
回答5:
I store my svn repository in a DropBox folder, which is a quick and dirty way to work on multiple computers without setting up a proper SVN server.
This only works if two people don't use it on different computers at the same time (it will get corrupted)
回答6:
No. Free source control hosting is widely available - dropbox isn't quicker than git or mercurial, although it is dirtier.
You might as well use RCS locally as use dropbox.
来源：https://stackoverflow.com/questions/2262190/is-dropbox-a-valid-quick-and-dirty-source-control-solution