Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

1. Commit Access

1.1. Configuration

The subversion server uses SSL client certificates to handle authentication of users. When you are granted commit access, you will be provided two files. These files should be placed in your ~/.subversion/ directory.

  1. Digium_SVN-cacert-sha1.pem
  2. <name>-cert.p12

The following should be placed in the ~/.subversion/servers file:


It is also recommended that you add the following to the ~/.subversion/config file. Otherwise, you will have problems using our tools for merging changes between branches.


1.2. SVN Checkouts

Checkouts that come from are read-only copies of the repositories. When doing a checkout that you intend to commit to, it must be from For example:

2. Using svnmerge for Cross-Branch Merging

2.1. Tools Installation

You must install svnmerge and the related wrappers from our repotools repository. The wrapper scripts use expect, so be sure to install that, too.

2.2. svnmerge Properties

If you do a svn pl -v while you are located in an svn checkout, you will see all the properties currently attached to the root directory. For instance, on a checked out copy of Asterisk trunk, you will see something like this:


and on the 1.8 branch, you will see these sort of properties:


These properties identify the following things:

  1. The branch changes are being merged from
    • branch-<branch>-...
  2. The revisions merged from that branch
    • branch-<branch>-merged:/branches/<branch>:<revisions>
  3. The revision explicitly not merged, or blocked, from that branch
    • branch-<branch>-blocked:/branches/<branch>:<revisions>

2.3. Branch Merging Order

When committing a change that applies to more than one branch, the change first goes into the oldest branch and is then merged up to the next one. If a branch is reached where the change should not be merged up, it should be explicitly blocked. The following diagram shows the current branch merge order.

Unknown macro: {flowchart}

"/svn/asterisk/branches/1.8" -> "/svn/asterisk/branches/1.10"
"/svn/asterisk/branches/1.10" -> "/svn/asterisk/trunk"

  • 1.2 -> 1.4
    • merge24 <revision>
    • block24 <revision>
  • 1.4 -> 1.6.2
    • merge46 <revision>
    • block46 <revision>
  • 1.6.2 -> 1.8
    • merge68 <revision>
    • block68 <revision>
  • 1.8 -> 1.10
    • merge810 <revision>
    • block810 <revision>
  • 1.10 -> trunk
    • merge10trunk <revision>
    • block10trunk <revision>

All of these scripts create a commit message for you in the file ../merge.msg. Run svn commit and use that commit message with the following command:


Sometimes when you go to commit your changes after merging from another branch, you will end up with a conflict. The conflict will typically be against . (period). To resolve the conflict, run svn resolved . prior to committing.

2.4. Backporting Changes

Sometimes a change is made in a branch and later it is decided that it should be backported to an older branch. For example, a change may have gone into the 1.8 branch and later needs to be backported to the 1.6.2 branch. To handle this, first manually make the change and commit to the 1.6.2 branch. Then, there is another wrapper similar to merge68 and block68 to record that the code from a revision already exists in the 1.8 branch. The wrapper is record68.

3. Developer Branches


If you have been granted workspace on the server, you will have read and electronically signed the Open Source Contributor License found at (upon signing in) and have been given an SSL client certificate.

Developer branches are stored in the /team/<name> directory of each project repository (and /team/<name>/private for private branches).

3.1. Creating a Developer Branch

Use the following commands to create a branch and prepare it for future merge tracking of the branch you created it from. This example creates a branch off of Asterisk trunk.

3.2. Group Branches

Group branches are developer branches intended to be worked on by more than one developer. Instead of putting them in /team/<name>, they go in the /team/group directory, instead. Otherwise, they're managed in the exact same way as other developer branches.

3.3. Automatically Keeping Branches Up to Date Using automerge

Our subversion server provides the ability to automatically keep developer branches up to date with their parent. To enable this feature, set the automerge and automerge-email properties on the root directory. Changes from the parent branch will be periodically (once an hour) merged into your branch. If a change from upstream conflicts with changes in the branch, the automerge process will stop and the address(es) listed in the automerge-email property will be notified.


Running svnmerge init and committing those properties is a prerequisite for automerge to work for a developer branch.

Use the following commands to enable automerge on a developer branch:

3.3.1. Setting automerge-email on a Group Branch

For a branch with multiple developers working on it, it may be useful to have automerge emails sent to more than one email address. To do so, just separate the email addresses in the property with commas. The value of this property is literally used as the content for the To: header of the email.

3.3.2. Resolving automerge Conflicts

If your developer branch goes into conflict with automerge on, and the automerge-email property has been set, you will receive an email notifying you of the conflict and automerge will be disabled. To resolve it, use the following commands:

Running the svnmerge tool will merge in the changes that cause your branch to go into conflict into your local copy. Edit the files that are in conflict to resolve the problems as appropriate. Finally, tell SVN that you have resolved the problem, re-enable automerge, and commit.

3.4. Private Branches

A private developer branch is only visible to Digium and the branch owner. Management of a private branch is exactly the same as any other developer branch. The only difference is branch location. Instead of putting the branch in /team/<name>/ the branch goes in /team/<name>/private/.

3.5. Merging a Developer Branch into trunk


If your branch contains new functionality, please make sure you have made the appropriate modifications to CHANGES and/or UPGRADE.txt.

If a developer has a branch that is ready to be merged back into the trunk, here is the process:


This is NOT using the svnmerge script; this is just a normal SVN merge.

Once this is done, the working copy will contain the trunk plus the changes from the developer branch. If you follow the above instructions for creating branches, you have probably introduced properties to the root of the branch that need to be removed.

If you are purposely introducing new properties, or purposely introducing new values for existing properties, then you might do the following instead, so as not to destroy your properties:

If everything merged cleanly, you can test compile and then:

Once the contents of your branch has been merged, please use svn remove to remove it from the repository. It will still be accessible if needed by looking back in the repository history if needed.

  • No labels