Subversion

Subversion is a version control system and used by ReactOS.

ReactOS source code was in a CVS repository up to December 30th 2004. Since January 1st 2005, the source code is in a Subversion (SVN) repository.

Access the sources

To download the sources, you will need an SVN client.

Source code locations:

• ReactOS documentation - svn://svn.reactos.org/reactos/trunk/documentation/ (documentation)
• ReactOS irc - svn://svn.reactos.org/reactos/trunk/irc/
• ReactOS press media - svn://svn.reactos.org/reactos/trunk/press-media/
• ReactOS - svn://svn.reactos.org/reactos/trunk/reactos (ReactOS Operating system)
• RosApps - svn://svn.reactos.org/reactos/trunk/rosapps (ReactOS Software on release version)
• ReactOS Wallpaper - svn://svn.reactos.org/reactos/trunk/wallpaper/
• ReactOS web - svn://svn.reactos.org/web/trunk (ReactOS web content)
• ReactOS amd64 - svn://svn.reactos.org/reactos/branches/ros-amd64-bringup/reactos

Windows

For Windows, it is recommended to use the TortoiseSVN client, which nicely integrates into the Windows Explorer.

Another SVN Client is the SVN command line client. This one is also bundled with the ReactOS Build Environment for Windows.

Other platforms

• The command line client for some other platforms is available here
• Subclipse (Plugin for Eclipse)

Browse the sources online

You can also view the sources in the repository online by visiting our ViewVC with a browser, or browse through a daily updated cross-referenced doxygen database.

Usage of the SVN clients

The usage of the SVN clients is described in a separate article for each client:

• TortoiseSVN
  • Using TortoiseSVN
  • Merging with TortoiseSVN
• other
  • Using the SVN command line client

Commit mails

Mails with changes in each commit are sent to the mailing list ros-diffs. They will be plain text mails, which contain the differences in this revision.

Read the Mailing Lists page for more information about the mailing lists.

Request commit (write) access

Prerequisites [WIP]

There are a few mandatory prerequisites to getting a direct, full write access (aka "commit access") to the main repository:

• Ability to communicate in written English.
• Be ready to disclose a full real name and postal address to at least the project's official (e.g. development lead or project lead), and preferably disclose full real name for public access.
• Have no legal restrictions related to contributing code to open source projects.

Applying for write access

Once you have started submitting patches and new code to the project you can be considered for application. We would prefer not to give access to someone who makes two or three updates and then never again. Also, if you are only going to submit patches now and again, you should file a bug in our Bugzilla and attach the patch file to it. If, however, you become a contributing developer on a continuing basis, you should definitely consider applying for write access.

Who to ask

Join the ReactOS IRC channel on FreeNode #reactos and ask.

Read ReactOS IRC Channels for more information

Troubleshooting

SVN Update says: Object with the same name already exists

When you update your working copy, you may get the error message object with the same name already exists.

Subversion displays the error message because the directory is replaced in the repository and your working copy contains data which is unknown to Subversion (Your working copy is locally modified). Since Subversion does everything it can to not cause harm to your data, you must remove or move the data which is not in the repository out of the working copy.

This scenario won't happen very often though. You have two options to correctly resolve the problem:

• Remove the affected directory and update your working copy again.
• Remove all files and directories in the working copy that are unknown to Subversion and then update your working copy again.

More information

A complete book about Subversion is available online at http://svnbook.red-bean.com.