Skip to content

Commit b7dd54a

Browse files
phil-blaingitster
authored andcommitted
git-merge.txt: modernize word choice in "True merge" section
The "True merge" section of the 'git merge' documentation mentions that in case of conflicts, the conflicted working tree files contain "the result of the "merge" program". This probably refers to RCS's 'merge' program, which is mentioned further down under "How conflicts are presented". Since it is not clear at that point of the document which program is referred to, and since most modern readers probably do not relate to RCS anyway, let's just write "the merge operation" instead. Signed-off-by: Philippe Blain <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 1ef3c61 commit b7dd54a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Documentation/git-merge.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@ happens:
194194
versions: stage 1 stores the version from the common ancestor,
195195
stage 2 from `HEAD`, and stage 3 from `MERGE_HEAD` (you
196196
can inspect the stages with `git ls-files -u`). The working
197-
tree files contain the result of the "merge" program; i.e. 3-way
197+
tree files contain the result of the merge operation; i.e. 3-way
198198
merge results with familiar conflict markers `<<<` `===` `>>>`.
199199
5. No other changes are made. In particular, the local
200200
modifications you had before you started merge will stay the

0 commit comments

Comments
 (0)