Dear Wiki user, You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.
The "MergeCodeImprovements" page has been changed by JulianFoad: http://wiki.apache.org/subversion/MergeCodeImprovements?action=diff&rev1=8&rev2=9 At present it uses ''svn_mergeinfo_t'' (and additional information) internally, but it might be better to change it to use an array of ''svn_repos_location_t'' or something else instead. At least it's wrapped a bit better for now. - A terrible example is the function ''combine_range_with_segments().'' It intersects a ''svn_merge_range_t'' with a list of ''svn_location_segment_t'' and produces a list of ''merge_source_t''. + A terrible example is the function ''combine_range_with_segments().'' It intersects a ''svn_merge_range_t'' with a list of ''svn_location_segment_t'' and produces a list of ''merge_source_t''. Three different types. === Prototype new merge code in Python === It would be extremely handy to be able to write new client-layer merge code in Python. The easiest way to start doing this would probably be to write a Python command-line program that implements the equivalent of "svn merge" and uses either the swig-Python bindings or the ctypes-Python bindings to access Subversion library APIs. (In particular, don't try to embed a Python merge module inside the 'svn' C program, unless somebody can show us how to do that quickly and easily.)
