Everyone who is working with Subversion using multiple branches knows this problem: Merging changes from branch A to branch B needs to be documented (in most cases in the log).
This can be risky as if one developer forgets to put that important information in the log, no one will ever see which change sets are now merged in branch B and following merges can cause lots of conflicts or loss of changes.
There is no automatic book keeping in Subversion - yet. In the upcoming release, Subversion 1.5 will provide merge tracking support.

I am really happy to see that great software gets even better!

Technorati Tags: merge tracking, subversion