Skip to content

Commit b2af482

Browse files
xfqgitster
authored andcommitted
user-manual: fix the description of fast-forward
The "Fast-forward merges" section of user-manual.txt incorrectly says if the current branch is a descendant of the other, Git will perform a fast-forward merge, but it should the other way around. Signed-off-by: Xue Fuqiao <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 282616c commit b2af482

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

Documentation/user-manual.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1431,11 +1431,11 @@ differently. Normally, a merge results in a merge commit, with two
14311431
parents, one pointing at each of the two lines of development that
14321432
were merged.
14331433

1434-
However, if the current branch is a descendant of the other--so every
1435-
commit present in the one is already contained in the other--then Git
1436-
just performs a "fast-forward"; the head of the current branch is moved
1437-
forward to point at the head of the merged-in branch, without any new
1438-
commits being created.
1434+
However, if the current branch is an ancestor of the other--so every commit
1435+
present in the current branch is already contained in the other branch--then Git
1436+
just performs a "fast-forward"; the head of the current branch is moved forward
1437+
to point at the head of the merged-in branch, without any new commits being
1438+
created.
14391439

14401440
[[fixing-mistakes]]
14411441
Fixing mistakes

0 commit comments

Comments
 (0)