Subversion mergeinfo loss after copy‑move

Mergeinfo loss after svn copy --no-recursive followed by svn move in Subversion 1.9+

0 reputation · 29 Jun 2024, 04:24 UTC

25.2K views0

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 duplicate revisions or spurious conflicts during later merges.

Questions:

Does svn copy --no-recursive preserve the source's svn:mergeinfo on the newly created target?
If mergeinfo is missing after the copy, does a following svn move automatically recover it to match the source's merge history?

2,958 following

Keep exploring this topic

Does svnadmin hotcopy lock the source repository during the copy operation?

Uncertainty remains about whether svnadmin hotcopy locks the source repository during copying, how hook scripts are handled, and if client relocation can occur without downtime.

Subversion 1.14 Timeout Directive and Client Retry Behavior

Discusses whether Subversion should standardize retry behavior for server‑enforced timeouts or leave it to wrappers, given version‑specific timeout directives and missing distinct error codes.

Subversion update behavior during tree conflict resolution

An analysis of how Subversion handles the interaction between 'svn update' and 'svn revert' when managing tree conflicts versus standard text conflicts.

Subversion sparse checkout depth and merge behavior

Analysis of how Apache Subversion handles merges when the target working copy uses sparse checkouts and specific depth settings.

Mergeinfo loss after svn copy --no-recursive followed by svn move in Subversion 1.9+

0 answers

Your perspective belongs here.

0 question comments