Separate projects should be kept in separate repositories. Putting multiple projects in the one repository is just asking for confusion. If things are related sufficiently then they're probably the same project.
That said, to solve the synchronisation of *working* space problem, you *could* put the whole thing inside your Dropbox folder. That isn't so good for large projects involving binary builds, but for scripting language projects, it's great. And then you don't have to worry about forgetting to commit code (and you should *also* be using a code repository, but it then fulfils its correct function - keeping a history of your code, as opposed to being misused for a function it's not designed for - keeping directories in sync).
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2011-08-11 02:54 am (UTC)That said, to solve the synchronisation of *working* space problem, you *could* put the whole thing inside your Dropbox folder. That isn't so good for large projects involving binary builds, but for scripting language projects, it's great. And then you don't have to worry about forgetting to commit code (and you should *also* be using a code repository, but it then fulfils its correct function - keeping a history of your code, as opposed to being misused for a function it's not designed for - keeping directories in sync).