Foreign Repository Copies

Some time ago, I wrote in this space about some new functionality that I had managed to work into Subversion — the ability to merge changes into a working copy from a so-called “foreign repository” (that is, a different repository than the one reflected by the working copy).  I touted the feature as a lovely alternative way to manage vendor branches.  I admit that I may have glossed over the details a bit in that post, but the idea seemed simple enough:  import a baseline copy of the third-party codebase into your repository, and thereafter merge the changes made by …

Read More »

Changes made from Subversion 1.4.x to 1.5 – A command line point of view

Command line comparison between Subversion 1.4.x and Subverson 1.5.

Nominate Subversion for product of the year

Nominate Subversion for product of the year

TortoiseSVN and Subversion 1.5

TortoiseSVN’s plans for Subversion 1.5

Subversion 1.5 WebDAV Write-Thru Proxies

With Subversion 1.5 you can implement master-slave server architectures whereby clients read from a slave and write (through the slave) to the master repository.

Considerations when upgrading to Subversion 1.5

Upgrade considerations for Subversion 1.5

Subversion 1.5 availability

When will Subversion 1.5 be available? Understand the process of how the Subversion community goes from development to release and get a weatherperson’s prediction.

Change Set Based Merges in Subversion

Download the GUI change set merge client for Subversion 1.5 from openCollabNet:

Subversion merge made easy

CollabNet released a preview of its GUI merge client for Subversion 1.5. You can find the software at

Subversion Merge Tracking – The Basics

Subversion 1.5 will support Merge Tracking. This blog post provides a high level overview of what Merge Tracking is, why it is important and what it means to your organization. It also suggest what you can do to prepare your organization and invites you to join the Merge Tracking Early Adopter Program