[PATCH 7 of 7] merge-tools: add a `premerge=merge3` config option
pierre-yves.david at ens-lyon.org
pierre-yves.david at ens-lyon.org
Tue Aug 5 00:28:13 UTC 2014
# HG changeset patch
# User Pierre-Yves David <pierre-yves.david at fb.com>
# Date 1407195161 25200
# Mon Aug 04 16:32:41 2014 -0700
# Node ID 7197e4663b200e2106e3cff83ac6d53dcc7a4c0c
# Parent 3becac234386b2ea0f5d70f906b4daa1f7e0e6ae
merge-tools: add a `premerge=merge3` config option
This value leaves premerge markers that includes the merge base too. This is a
the same as what `internal:merge3` would do.
diff --git a/mercurial/filemerge.py b/mercurial/filemerge.py
--- a/mercurial/filemerge.py
+++ b/mercurial/filemerge.py
@@ -176,11 +176,11 @@ def _premerge(repo, toolconf, files, lab
return 1
a, b, c, back = files
ui = repo.ui
- validkeep = ['keep']
+ validkeep = ['keep', 'keep-merge3']
# do we attempt to simplemerge first?
try:
premerge = _toolbool(ui, tool, "premerge", not binary)
except error.ConfigError:
@@ -190,10 +190,15 @@ def _premerge(repo, toolconf, files, lab
raise error.ConfigError(_("%s.premerge not valid "
"('%s' is neither boolean nor %s)") %
(tool, premerge, _valid))
if premerge:
+ if premerge == 'keep-merge3':
+ if not labels:
+ labels = _defaultconflictlabels
+ if len(labels) < 3:
+ labels.append('base')
r = simplemerge.simplemerge(ui, a, b, c, quiet=True, label=labels,
no_minimal=True)
if not r:
ui.debug(" premerge successful\n")
return 0
diff --git a/mercurial/help/config.txt b/mercurial/help/config.txt
--- a/mercurial/help/config.txt
+++ b/mercurial/help/config.txt
@@ -910,12 +910,14 @@ Supported arguments:
commit being rebased.
Default: ``$local $base $other``
``premerge``
Attempt to run internal non-interactive 3-way merge tool before
- launching external tool. Options are ``true``, ``false``, or ``keep``
- to leave markers in the file if the premerge fails.
+ launching external tool. Options are ``true``, ``false``, ``keep`` or
+ ``keep-merge3``. The ``keep`` option will leave markers in the file if the
+ premerge fails. The ``keep-merge3`` will do the same but incluses information
+ about the base of the merge in the marker (see internal:merge3)
Default: True
``binary``
This tool can merge binary files. Defaults to False, unless tool
was selected by file pattern match.
diff --git a/tests/test-merge-tools.t b/tests/test-merge-tools.t
--- a/tests/test-merge-tools.t
+++ b/tests/test-merge-tools.t
@@ -681,10 +681,11 @@ Default is silent simplemerge:
space
revision 3
# hg stat
M f
+
.premerge=False executes merge-tool:
$ beforemerge
[merge-tools]
false.whatever=
@@ -739,10 +740,48 @@ Default is silent simplemerge:
revision 4
>>>>>>> other: 81448d39c9a0 - test: revision 4
# hg stat
M f
+.premerge=keep-merge3 keeps conflict markers with base content:
+
+ $ beforemerge
+ [merge-tools]
+ false.whatever=
+ true.priority=1
+ true.executable=cat
+ # hg update -C 1
+ $ hg merge -r 4 --config merge-tools.true.premerge=keep-merge3
+ merging f
+ <<<<<<< local: ef83787e2614 - test: revision 1
+ revision 1
+ space
+ ||||||| base
+ revision 0
+ space
+ =======
+ revision 4
+ >>>>>>> other: 81448d39c9a0 - test: revision 4
+ revision 0
+ space
+ revision 4
+ 0 files updated, 1 files merged, 0 files removed, 0 files unresolved
+ (branch merge, don't forget to commit)
+ $ aftermerge
+ # cat f
+ <<<<<<< local: ef83787e2614 - test: revision 1
+ revision 1
+ space
+ ||||||| base
+ revision 0
+ space
+ =======
+ revision 4
+ >>>>>>> other: 81448d39c9a0 - test: revision 4
+ # hg stat
+ M f
+
Tool execution
set tools.args explicit to include $base $local $other $output:
More information about the Mercurial-devel
mailing list