mirror of
https://github.com/git/git
synced 2024-07-17 02:57:48 +00:00
b1889c36d8
Since the git-* commands are not installed in $(bindir), using "git-command <parameters>" in examples in the documentation is not a good idea. On the other hand, it is nice to be able to refer to each command using one hyphenated word. (There is no escaping it, anyway: man page names cannot have spaces in them.) This patch retains the dash in naming an operation, command, program, process, or action. Complete command lines that can be entered at a shell (i.e., without options omitted) are made to use the dashless form. The changes consist only of replacing some spaces with hyphens and vice versa. After a "s/ /-/g", the unpatched and patched versions are identical. Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
43 lines
937 B
Plaintext
43 lines
937 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
|