Show More
@@ -97,7 +97,7 b' def show_doc(ui):' | |||||
97 | ui.write("\n") |
|
97 | ui.write("\n") | |
98 |
|
98 | |||
99 | section(ui, _("Extensions")) |
|
99 | section(ui, _("Extensions")) | |
100 |
ui.write(_("This section contains help for extensions that |
|
100 | ui.write(_("This section contains help for extensions that are distributed " | |
101 | "together with Mercurial. Help for other extensions is available " |
|
101 | "together with Mercurial. Help for other extensions is available " | |
102 | "in the help system.")) |
|
102 | "in the help system.")) | |
103 | ui.write("\n\n" |
|
103 | ui.write("\n\n" |
@@ -7,8 +7,9 b' made on both branches.' | |||||
7 |
|
7 | |||
8 | The merge tools are used both for :hg:`resolve` and :hg:`merge`. |
|
8 | The merge tools are used both for :hg:`resolve` and :hg:`merge`. | |
9 |
|
9 | |||
10 |
Usually, the merge tool tries to automatically |
|
10 | Usually, the merge tool tries to automatically reconcile the files by | |
11 |
non-overlapping changes that occurred separately in |
|
11 | combining all the non-overlapping changes that occurred separately in | |
|
12 | the two different | |||
12 | evolutions of the same initial base file. Furthermore, some |
|
13 | evolutions of the same initial base file. Furthermore, some | |
13 | interactive merge programs make it easier to manually resolve |
|
14 | interactive merge programs make it easier to manually resolve | |
14 | conflicting merges, either in a graphical way, or by inserting some |
|
15 | conflicting merges, either in a graphical way, or by inserting some | |
@@ -41,10 +42,10 b' merge tools are:' | |||||
41 | ``internal:dump`` |
|
42 | ``internal:dump`` | |
42 | Creates three versions of the files to merge, containing the |
|
43 | Creates three versions of the files to merge, containing the | |
43 | contents of local, other and base. These files can then be used to |
|
44 | contents of local, other and base. These files can then be used to | |
44 |
perform a merge manually. If the file merged is name |
|
45 | perform a merge manually. If the file to be merged is named | |
45 | these files will accordingly be named ``a.txt.local``, |
|
46 | ``a.txt``, these files will accordingly be named ``a.txt.local``, | |
46 | ``a.txt.other`` and ``a.txt.base`` and they will be placed in the |
|
47 | ``a.txt.other`` and ``a.txt.base`` and they will be placed in the | |
47 |
same directory as |
|
48 | same directory as ``a.txt``. | |
48 |
|
49 | |||
49 | How Mercurial decides which merge program to use |
|
50 | How Mercurial decides which merge program to use | |
50 |
|
51 | |||
@@ -77,8 +78,8 b' 7. The merge fails.' | |||||
77 | to merge the files using a simple merge algorithm first, to see if |
|
78 | to merge the files using a simple merge algorithm first, to see if | |
78 | they can be merged without conflicts. Only if there are conflicting |
|
79 | they can be merged without conflicts. Only if there are conflicting | |
79 | changes Mercurial will actually execute the merge program. Whether |
|
80 | changes Mercurial will actually execute the merge program. Whether | |
80 |
to use the simple merge algorithm first can be controlled b |
|
81 | to use the simple merge algorithm first can be controlled by the | |
81 |
premerge setting of the merge tool |
|
82 | premerge setting of the merge tool. Premerge is enabled by default | |
82 | unless the file is binary or symlink. |
|
83 | unless the file is binary or symlink. | |
83 |
|
84 | |||
84 | See the merge-tools and ui sections of hgrc(5) for details on |
|
85 | See the merge-tools and ui sections of hgrc(5) for details on |
General Comments 0
You need to be logged in to leave comments.
Login now