Topics ▾
Email
Version 1.5.3 ▾
git-merge-base last updated in 1.8.0
Changes in the git-merge-base manual
Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Administration
Server Admin
Plumbing Commands
- 1.8.0.1 → 1.8.2.3 no changes
-
1.8.0
10/21/12
- 1.7.5.3 → 1.7.12.4 no changes
-
1.7.5.2
05/20/11
- 1.7.5.1 no changes
-
1.7.5
04/24/11
- 1.7.3.1 → 1.7.4.5 no changes
-
1.7.3
09/18/10
- 1.6.5.1 → 1.7.2.5 no changes
-
1.6.5
10/10/09
- 1.6.1.1 → 1.6.4.5 no changes
-
1.6.1
12/25/08
- 1.6.0.1 → 1.6.0.6 no changes
-
1.6.0
08/17/08
- 1.5.6.1 → 1.5.6.6 no changes
-
1.5.6
06/18/08
- 1.5.4.1 → 1.5.5.6 no changes
-
1.5.4
02/02/08
- 1.5.3.1 → 1.5.3.8 no changes
-
1.5.3
09/02/07
git-merge-base(1) Manual Page
NAME
git-merge-base - Find as good common ancestors as possible for a merge
SYNOPSIS
git-merge-base [--all] <commit> <commit>
DESCRIPTION
"git-merge-base" finds as good a common ancestor as possible between the two commits. That is, given two commits A and B git-merge-base A B will output a commit which is reachable from both A and B through the parent relationship.
Given a selection of equally good common ancestors it should not be relied on to decide in any particular way.
The "git-merge-base" algorithm is still in flux - use the source...
OPTIONS
- --all
Output all common ancestors for the two commits instead of just one.
Author
Written by Linus Torvalds <torvalds@osdl.org>
Documentation
Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
GIT
Part of the git7 suite