In brief
git merge-base finds suitable common ancestors for merging commits. A pair can have more than one best common base.
Useful to know
git merge-base finds suitable common ancestors for merging commits. A pair can have more than one best common base. [1]
This helps explain where changes diverged, but is not merely a date comparison. History is a graph of relationships. To check whether one revision precedes another, use ancestry semantics rather than only the older timestamp.
Sources
For further detail and to check the information: