- Quinn
On Jul 8, 2009, at 3:31 AM, Kez wrote:
As you have things already organized by client, I would say that it would be better to go for the repository per client. This would be dependant on how much versioning/rollbacks/merges required is required. So in effect you would have a subfolder for each project you have done for a client in their Repository. Obviously YMMV and you have to make a decision on how much you will be relying on the versioning system for what you need and changes you will be making per project on a regular basis. Kieren On 07/07/2009, at 7:42 PM, Mitch Cohen wrote:Newbie question. I have a slew of existing projects which are strictly local (no SVN at all). Most are web projects, some XCode.They are scattered all over my hard drive (organized by client) I nowhave Versions, and a hosted subversion account. I'd like to get all my projects under SVN. I'm the only coder on any of these projects. What are the pros/cons of: -Having one hosted repository, with folders for each of my projects -Many hosted repositories, each for one of my projects? Thanks!--~--~---------~--~----~------------~-------~--~----~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 -~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature