summaryrefslogtreecommitdiffstats
path: root/git-merge-base.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2008-07-06 05:20:31 +0000
committerJunio C Hamano <junio@hera.kernel.org>2008-07-06 05:20:31 +0000
commitba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch)
tree390507328a7564b65dc803683c34235700b97409 /git-merge-base.txt
parent05bf9c54a827e48b2b576488f5170a3490b5180e (diff)
downloadgit-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz
Autogenerated HTML docs for v1.5.6.2-212-g08b5
Diffstat (limited to 'git-merge-base.txt')
-rw-r--r--git-merge-base.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-merge-base.txt b/git-merge-base.txt
index 41fb0c76a..1a7ecbf8f 100644
--- a/git-merge-base.txt
+++ b/git-merge-base.txt
@@ -13,7 +13,7 @@ SYNOPSIS
DESCRIPTION
-----------
-`git-merge-base` finds as good a common ancestor as possible between
+'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.
@@ -21,7 +21,7 @@ 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...
+The 'git-merge-base' algorithm is still in flux - use the source...
OPTIONS
-------