14. Interactions between FreeBSD Subversion and Perforce
Prev |  | Next

## 14. Interactions between FreeBSD Subversion and Perforce

The FreeBSD Perforce and Subversion repositories are completely separate. However, changes to Subversion are tracked at near-real-time in Perforce. Every 2 minutes, the Subversion server is polled for updates in the HEAD branch, and those updates are committed to Perforce in the `//depot/vendor/freebsd/...` tree. This tree is then available for branching and integrating to derivative projects. Any project that directly modifies that FreeBSD source code should have this tree as its branch parent (or grandparent, depending on the needs), and periodic integrations and syncs should be done so that your tree stays up to date and avoids conflicts with mainline development.

The bridge between Subversion and Perforce is one-way; changes to Subversion will be reflected in Perforce, but changes in Perforce will not be reflected in Subversion. On request, some parts of the Perforce repo can be exported to CVSup and made available for distribution that way. Contact the FreeBSD Perforce administrators if this is something that you are interested in.

Prev |  | Next
13. Renaming files | Home | 15. Offline Operation

This, and other documents, can be downloaded from http://ftp.FreeBSD.org/pub/FreeBSD/doc/

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.