In terms of organization, we've created a separate repo per client, which in turn has folders for individual projects. Sometimes there are multiple folders within a project for different sub-projects.On the next level you have your branches, tags, trunk, and so and so forth. We've used this structure for a while now and its worked out quite well.
On Jun 7, 5:31 pm, Chris Sanders <sanderstu...@gmail.com> wrote: > I'm trying to figure out what's the best way to setup a repository for > multiple clients? > 1) Should I just create one repository for every client > 2) Should I make one repository and put all the clients into that? > > Because I'd like to set it up in a way that when I need to allow an > external developers on a project, i can control which accounts they > work, there by not giving access to everyone elses accounts. > > Thanks > Chris Sanders --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. 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 -~----------~----~----~----~------~----~------~--~---
