Automating Merge Tracking with Subversion svn:mergeinfo
Use svn:mergeinfo to automate pending-merge detection in Subversion, with CI-controlled updates, pre-commit guards, and drift checks between recorded and actual merges.
Loading…
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use svn:mergeinfo to automate pending-merge detection in Subversion, with CI-controlled updates, pre-commit guards, and drift checks between recorded and actual merges.
Goal: preserve accurate svn:mergeinfo when reorganizing a branch by first copying a subtree with svn copy --no-recursive and then moving the copied subtree with svn move. Uncertainty: the --no-recursive flag may prevent mergeinfo from being set on the new copy, and the subsequent move might not restore the original merge tracking data, potentially causing du
Goal Investigate how Subversion records merge ranges when multiple merge operations target the same branch concurrently. Background Subversion’s merge tracking uses the svn:mergeinfo property, which stores revision ranges applied to a path. The current implementation lacks a documented policy for handling overlapping ranges that arise from concurrent merges.