On Wed, Oct 15, 2008 at 08:59, Graham Leggett <[EMAIL PROTECTED]> wrote: > Hilco Wijbenga wrote: >> 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.
Smells like YAGNI except for the "disk space at a premium" below. > 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. That's the only good reason I can see: projects that are so inherently different that sharing is not going to happen. > This can also be important where disk space is at a premium, such as when > disk space is hosted by a third party. Fair enough (although I would be very uncomfortable having the crown jewels under the control of some 3rd party). You mention a very special use case for which I would agree with your assessment. Usually, Subversion stores code in a local environment and multiple repositories don't make sense there. It's just more work. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
