Re: One repository per project, or subfolders?

[Quinn Taylor]

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.)

 - Quinn

On Jul 9, 2009, at 6:09 AM, Jamie wrote:

I doubt that network congestion would necessarily be reduced by using a single repository, since Versions checks for each working copy individually anyway.

The setup I use is a single repository with folders for each client
underneath a folder for each project for that client. No need for
multiple repositories. You can check out a working copy of any project
anywhere you'd like. Network congestion, e.g. checking status, can be
limited if you do this verses checking out the entire repository.

There are plenty of options for arrangement, none are wrong, some
maybe more usable than others for various reasons with various pros/
cons for each.

Jamie

On Jul 8, 9:57 am, Mitch Cohen <mitchellsco...@gmail.com> wrote:

Thanks everyone! I hadn't thought about the one client per repository

notion, but that makes a lot of sense.

Thanks again!

--~--~---------~--~----~------------~-------~--~----~

To post to this group, send email to versions@googlegroups.com
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en
-~----------~----~----~----~------~----~------~--~---

You received this message because you are subscribed to the Google Groups "Versions" group.

smime.p7s
Description: S/MIME cryptographic signature