merge_in results in several revisions not on revision with several changes in the changeset

tmlab / majortom

The MaJorToM ( Merging Topic Maps Engine ) project was founded to develop a lightweight, merging and flexible Topic Maps engine satisfying different business use cases. The engine provides a couple of new features above to other engines based on the Topic Maps API version 2.0.

1 stars 1 forks source link

merge_in results in several revisions not on revision with several changes in the changeset #61

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. tm1.merge_in(tm2)

What is the expected output? What do you see instead?
one revision with a changeset inluding several changes that describe what 
happened during merge. Instead: several revisions.

Original issue reported on code.google.com by schulze....@googlemail.com on 21 Sep 2010 at 2:18

GoogleCodeExporter commented 9 years ago

Original comment by Sven.Kro...@googlemail.com on 18 Feb 2011 at 6:13

Added labels: Milestone-1.2.0

GoogleCodeExporter commented 9 years ago

all changes of an merge in command are stored within one association

Original comment by Sven.Kro...@googlemail.com on 4 Apr 2011 at 9:40

Changed state: Fixed