5,418
edits
Changes
From Gramps
m
→Purpose of this tool
A situation that occurs occasionally is after giving someone a copy of your tree in our native [[Gramps XML]] format. Then each person makes changes to the copy in their possession using Gramps locally. You can't just give the person a fresh copy of your Tree because then their changes would be overwritten.
Programmers call this 'forking,.' (As in we : when travelers come to a 'fork in the road' and each chooses different paths.) You end up with But the bottom line is that you now have two trees derived from a common Tree.
At some point, you may want to merge the forks into a common tree... without losing the useful changes from either tree. That synchronization is what this tool is designed to facilitate. It depends on the two Trees sharing common IDs to simplify ignoring unchanged records. Then it focuses you on just the changes.
