On Sun, 09 Jul 2006, Kamesh Jayachandran wrote:
...
> If the first merge is revert, 'svn:mergeinfo' is not getting recorded.
>
> * subversion/libsvn_client/diff.c
> (update_wc_merge_info):
> If there is no 'svn:mergeinfo' recorded already and the merge is a revert
> make use of the passed in 'ranges' for 'svn:mergeinfo' calculation.
...
> @@ -1751,9 +1751,14 @@
>
> if (is_revert)
> {
> - ranges = svn_rangelist_dup(ranges, pool);
> - SVN_ERR(svn_rangelist_reverse(ranges, pool));
> - SVN_ERR(svn_rangelist_remove(&rangelist, ranges, rangelist, pool));
> + if (rangelist->nelts == 0)
> + rangelist = ranges;
> + else
> + {
> + ranges = svn_rangelist_dup(ranges, pool);
> + SVN_ERR(svn_rangelist_reverse(ranges, pool));
> + SVN_ERR(svn_rangelist_remove(&rangelist, ranges, rangelist, pool));
> + }
> }
> else
> SVN_ERR(svn_rangelist_merge(&rangelist, rangelist, ranges, pool));
This would record a reversed rangelist (e.g. "/trunk: 10-9, 7-5").
If a range list (e.g. "10-9, 7-5") for a merge source (e.g. "/trunk")
is not recorded in a WC's merge info, it's implied that either there
have been no merges from that source, or that merges haven't been
recorded. Either way, I'm not really seeing why we should record the
"reverted" range, as they either weren't already merged (likely a
no-op?), or there's no history of them being merged (meaning we've no
merge history to adjust).
- application/pgp-signature attachment: stored
Received on Mon Jul 10 09:09:12 2006