<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi, everyone, Thanks for all the feedback. I really do appreciate it. Now I need some more. I have the SVN manual suggested by Charles and have been reading it. I have an operational repository at work. I've put in a couple of files, verified that they are there, and retrieved them. However, I still need a bit of help (possibly a lot of help) to get a functional understanding for a real development effort. I need to know what the process looks like for a set of files, and -- more specifically -- what the process looks like when there are multiple developers working on the same project, or, worse, the same file. If you can provide a couple of step-by-step examples of how subversion is used on a daily basis, that would be particularly helpful. [Yes, I'm reading that part of the manual, but it's the biggest part of the manual and a shorter summary would help for my immediate needs.] When I'm trying to learn something, I have to read to get the concepts, listen to what other people tell me they have done, and then spend time actually doing. I have the following understanding at this point. Please feel free to correct me if my understanding is inaccurate. 1) I assume that each separate project, when created, is kept in a different folder in the repository, and, when created, begins its own trunk of code (set of files for the project) which are subsequently modified and after the first time any given file is placed in the repository, only changes to that file are retained by subversion. 2) Branches are the modifications to the initial trunk of code that have been saved as "stable, working" versions, that are identified / labeled as "milestones" for want of a better word, and which can be referenced as needed to retrieve specific versions of the project (trunk). 3) Tags are used to identify (i.e. label) these branches at the point that the code is evaluated as being stable and working. Someone indicated that even after a tag has been applied to a branch of code the branch can continue to be changed. This confuses me. I would have expected that once a tag has been associated with a branch of code, that it's really a milestone along the trunk that can be used to revert to a previous version of the project's code and therefore would NOT be changed as part of that tag. Please advise. Can anyone give me some sense of how fast the content grows? I have an application written in Visual FoxPro that's about 7Mb. A couple of others written in VB.Net that will be about 4Mb an 10Mb of source code respectively. What kinds of growth rates are you seeing? The repository is currently limited to 4Gb of space. Am I likely to run out of space in the foreseeable future? Again, any help will be much appreciated. Thanks in advance. Frank </body> </html>