Comparison graph

Abstract

A comparison graph is disclosed. A system for comparing code branches comprises a code branch separator for determining a first set of commits in a first code branch that are not common to a second code branch, and determining a second set of commits in the second code branch that are not common to the first code branch; and a user interface determiner for determining a display of the first set of commits and the second set of commits.

What is claimed is: 
     
         1 . (canceled) 
     
     
         2 . A method for determining and graphically representing commonality between a first code branch and a second code branch, comprising:
 determining that a commit in the first code branch is a merge base for the first code branch and the second code branch;   if the commit in the first code branch is a merge base, determining that a commit in the second branch is another merge base; and   if the commit in the second branch is another merge base, rendering data from the first code branch and data from the second code branch on a comparison graph, wherein the comparison graph includes at least one symbol representing a state of commits in the first code branch and the second code branch.   
     
     
         3 . The method of  claim 2 , further comprising:
 determining the merge base of the first code branch and the second code branch; and   subsequent to the determination of the merge base, selecting a first code branch commit.   
     
     
         4 . The method of  claim 3 , wherein the selection of a first code branch commit includes receiving data associated with the first code branch and selecting a most recent first commit data. 
     
     
         5 . The method of  claim 3 , further comprising, subsequent to the selection of the first code branch commit, receiving a selected first code branch commit. 
     
     
         6 . The method of  claim 2 , further comprising determining that a commit in the first code branch is not a merge base for the first code branch and the second code branch. 
     
     
         7 . The method of  claim 6 , further comprising if the first code branch is not a merge base for the first code branch and the second code branch, adding the commit in the first code branch to first branch data. 
     
     
         8 . The method of  claim 6 , further comprising if the first code branch is not a merge base for the first code branch and the second code branch:
 adding the commit in the first code branch to first branch data; and   selecting a next first code branch commit.   
     
     
         9 . The method of  claim 2 , further comprising, subsequent to the determination that a commit in the first code branch is a merge base for the first code branch and the second code branch, selecting a first second code branch commit. 
     
     
         10 . The method of  claim 2 , further comprising, subsequent to the determination that a commit in the first code branch is a merge base for the first code branch and the second code branch, receiving a selected second code branch commit. 
     
     
         11 . The method of  claim 2 , further comprising determining that a commit in the second code branch is not a merge base for the first code branch and the second code branch. 
     
     
         12 . The method of  claim 11 , further comprising if the first code branch is not a merge base for the first code branch and the second code branch, adding the commit in the second code branch to second branch data. 
     
     
         13 . The method of  claim 11 , further comprising if the first code branch is not a merge base for the first code branch and the second code branch:
 adding the commit in the second code branch to second branch data; and   selecting a next second code branch commit.   
     
     
         14 . A method for determining and graphically representing commonality between a first code branch and a second code branch, comprising:
 receiving a first set of commits, wherein the first set is associated with the first code branch;   receiving a second set of commits, wherein the second set is associated with the second code branch;   filtering at least one of the first set and the second set, including:
 for a selected commit of the first set, determining that the selected commit is a member of the second set; 
 if the selected commit is a member of the second set, removing the selected commit from the first set and the second set; and 
 determining that those remaining commits in the first set are not in common with those remaining commits in the second set; and 
   rendering the at least one of the first set and the second set on a comparison graph, wherein each of the commits is represented by a symbol representing a state of the commit.   
     
     
         15 . The method of  claim 14 , wherein the rendering the at least one of the first set and the second set on a comparison graph includes providing remaining commits of the first set of commits as the first set of commits in the first code branch that are not common to the second code branch. 
     
     
         16 . The method of  claim 14 , wherein the rendering the at least one of the first set and the second set on a comparison graph includes providing remaining commits of the second set of commits as the second set of commits in the second code branch that are not common to the first code branch. 
     
     
         17 . The method of  claim 14 , further comprising, prior to the filtering, selecting a next commit of the first code branch. 
     
     
         18 . The method of  claim 14 , wherein the filtering further includes: if the selected commit is a member of the second set, the commit is indicated as a merge base. 
     
     
         19 . The method of  claim 14 , further comprising requesting a merge base from a server. 
     
     
         20 . A method for determining and graphically representing commonality between a first code branch and a second code branch, comprising:
 determining whether a commit in the first code branch is a merge base for the first code branch and the second code branch;   if the commit in the first code branch is a merge base, determining whether a commit in the second branch is another merge base; and   if a commit in a second code branch is another merge base, rendering data from the first code branch and data from the second code branch on a comparison graph, wherein the comparison graph includes at least one symbol representing a state of commits in the first code branch and the second code branch.