# HG changeset patch # User Siddharth Agarwal # Date 1400875831 25200 # Node ID 6062593d8b06aaacd6e5e9eb9e84acff69ba038b # Parent 0c407790593291e8dddf4f7d226b2edf808981e6 resolve: don't abort resolve -l even when no merge is in progress This broke some internal automation that was quite reasonably checking for unresolved files as a way to determine whether a merge happened cleanly. We still abort for resolve --mark etc. diff -r 0c4077905932 -r 6062593d8b06 mercurial/commands.py --- a/mercurial/commands.py Sun May 25 13:47:42 2014 +0200 +++ b/mercurial/commands.py Fri May 23 13:10:31 2014 -0700 @@ -4922,7 +4922,7 @@ ms = mergemod.mergestate(repo) - if not ms.active(): + if not ms.active() and not show: raise util.Abort(_('resolve command not applicable when not merging')) m = scmutil.match(repo[None], pats, opts) diff -r 0c4077905932 -r 6062593d8b06 tests/test-histedit-non-commute-abort.t --- a/tests/test-histedit-non-commute-abort.t Sun May 25 13:47:42 2014 +0200 +++ b/tests/test-histedit-non-commute-abort.t Fri May 23 13:10:31 2014 -0700 @@ -85,8 +85,6 @@ log after abort $ hg resolve -l - abort: resolve command not applicable when not merging - [255] $ hg log --graph @ changeset: 6:bfa474341cc9 | tag: tip diff -r 0c4077905932 -r 6062593d8b06 tests/test-resolve.t --- a/tests/test-resolve.t Sun May 25 13:47:42 2014 +0200 +++ b/tests/test-resolve.t Fri May 23 13:10:31 2014 -0700 @@ -42,9 +42,12 @@ no more unresolved files $ hg commit -m 'resolved' -resolve -l should error since no merge in progress +resolve -l should be empty $ hg resolve -l + +resolve -m should abort since no merge in progress + $ hg resolve -m abort: resolve command not applicable when not merging [255] diff -r 0c4077905932 -r 6062593d8b06 tests/test-shelve.t --- a/tests/test-shelve.t Sun May 25 13:47:42 2014 +0200 +++ b/tests/test-shelve.t Fri May 23 13:10:31 2014 -0700 @@ -262,8 +262,6 @@ summary: second $ hg resolve -l - abort: resolve command not applicable when not merging - [255] $ hg status A foo/foo ? a/a.orig