Hilco Wijbenga wrote:
You shouldn't create multiple repositories without *very* good reasons. Multiple repositories just means having to duplicate authentication, backup setup, etcetera. Moreover, any kind of copying between projects is much harder that way. If you are working on multiple projects you'll eventually run into refactoring cases where you want multiple projects to reuse some shared code. That's a no-brainer in one repository but all but impossible (i.e. without losing history) in multiple repositories.And what do you gain? There's little advantage to having a repository per project.
One of the key advantages of having one repository per project is the ability to take a particular project offline and archive it at some point in the future.
This is important in setups where disk space use is likely to be significant over time, such as when working with graphics within a project, or other binary data that cannot be efficiently stored as diffs.
This can also be important where disk space is at a premium, such as when disk space is hosted by a third party.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
