One example for using a single repository is sandboxing. This repository is separate from the client's, may utilize a different SCM, access is limited, it may or may not be local but is always under your control.
Regarding network congestion, my point wasn't that it would be reduced using a single repository but that a single repository can lead to sluggish response as SVN determines status, e.g. creating a working copy of trunk/ and therefore all projects below it. As you correctly point out and apparently not clear in my statement, it's is not necessarily a result of a single repository but poor working practice. On a side note, with Xcode 3+ sandboxing can be achieved using the "Make Snapshot" feature. Jamie On Jul 9, 1:09 pm, Quinn Taylor <[email protected]> wrote: > That also works. The reason that use separate repositories is so that > work for separate clients is never intermingled together, and it's > simple to control access to a particular client's work. (Companies > tend to not like their IP to be freely available to other clients, > competitor or otherwise.) > > I doubt that network congestion would necessarily be reduced by using > a single repository, since Versions checks for each working copy > individually anyway. > > - Quinn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
