Answers to Frequently-Asked Questions

I changed the name of a file and now Revision Manager does not recognize it. Why not?

If you need to change the name of a file or folder in a working copy, you must use the rename option in a Revision Manager file window. Using Microsoft Windows Explorer or the MacOSX Finder to rename a revision controlled file might cause problems. Using one of these to rename a folder will almost certainly cause problems.

What is the .svn folder used for?

Each folder in a working copy contains a folder called .svn. The Revision Manager uses this folder to keep track of changes to the working copy. If you delete this folder, move the folder, or modify the contents of the folder then the working copy will become corrupt and you will probably be unable to synchronize with the repository.

Why does my working copy take up so much disk space?

A working copy requires space for about twice the size of the files and folders you want to check out. This is because the working copy contains not only the files you check out, but also a hidden snapshot of those files (located in the .svn folders). The snapshot makes it possible for Revision Manager to track many change operations without having to contact the repository.

How often should I commit changes from my working copy?

As often as you need to. Perhaps once per day. Perhaps when you finish a significant chunk of work. Perhaps when you are ready to communicate your work to someone else.

When should i create a branch?

When you need it. This is somewhat like organizing files into folders. Do not create folders unless you need them, then create a folder hierarchy that makes sense. You might know the hierarchy based on experience, but if this is something new, let it evolve. If you create too many branches up front, you may complicate things unnecessarily.

How do i know whether to use a single branch or multiple branches to do design variations?

It depends. here are some ways to organize design variations:

  • one branch per variant, with multiple people working in each branch
  • one branch per variant, with multiple child branches for each person
  • one branch per person, with design variants spaced over time and marked by tags

Should I create a branch for each person?

It depends on how much overlap there is between participants and how difficult it is to merge their work. A branch for each person works well if there is not much coupling between the things people are working on. If the parts are tightly coupled, a single branch might be better so that participants get immediate feedback about the effects their changes have on other participants.

When should I merge things to the trunk?

When it makes sense. If you are exploring design alternatives on different branches as a purely exploratory analysis, then you might never merge to the trunk. If the trunk represents the 'reference' release of a system, then the system engineer should manage the merge from one or more of the branches, using a testing/validation scheme to assure that the merged items satisfy requirements.

Does the structure of the contents of my branches have to match that of the trunk?

No. Some projects have the same structure across all branches. In other projects, the structure of each branch is a subset of the contents of the trunk.

What are the possible status indicators?

In a working copy:
  • A - marked for add
  • D - marked for delete
  • G - merged
  • R - replaced
  • C - conflict
In a history:
  • A - added
  • D - deleted
  • G - merged
  • R - replaced

How do I make Revision Manager see my existing working copies?

In the Preferences, select the 'Working Copies' panel. Select or enter the path to a folder above your working copies, then click the scan button.