483bc4f045
Following what appears to be the predominant style, format
names of commands and commandlines both as `teletype text`.
While we're at it, add articles ("a" and "the") in some
places, italicize the name of the command in the manual page
synopsis line, and add a comma or two where it seems appropriate.
Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
43 lines
938 B
Plaintext
43 lines
938 B
Plaintext
git-merge-base(1)
|
|
=================
|
|
|
|
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 linkgit:git[1] suite
|