until all revision events have been analyzed additionally if the revision event is determined to be u201c submit changes to parent u201d 510 subsequent revision events on the parent branch are analyzed 511 to identify a u201c merge changes from child u201d revision event corresponding to revision event on the user branch 512 if no revision event is identified the previously created version descriptor in the user branch summary is updated to include the current revision information identifying the pending state of the u201c merge requested u201d 513 if a subsequent u201c merge changes from child u201d revision event is identified on the parent branch corresponding to the revision event 508 on the user branch the previously created version descriptor in the user branch summary 402 is updated to include the current revision information identifying the resolved state of the u201c merged u201d revision event 514 the process iterates through the analysis of each more recent revision event 501 on the user branch until all revision events have been analyzed additionally if the revision event 501 is determined to be u201c share with child u201d corresponding to one or more child branches 515 the previously created version descriptor in the user branch summary is updated to include the current revision event information identifying the shared status on the user branch and an additional version descriptor on each of the child branch summaries is then added 516 the process iterates.