# HG changeset patch # User Pierre-Yves David # Date 1554496087 -7200 # Node ID 256b28ce03e318491ed5d79946c58ad7fc68a5fe # Parent 931c8f6f4b1be6ea9e2a46062ddc1698748f37cb next: clarify tests related to `commands.update.check` test This clarify the test and help understand the next changeset. diff -r 931c8f6f4b1b -r 256b28ce03e3 tests/test-prev-next.t --- a/tests/test-prev-next.t Wed Apr 03 17:20:34 2019 +0800 +++ b/tests/test-prev-next.t Fri Apr 05 22:28:07 2019 +0200 @@ -444,8 +444,14 @@ Test that --merge still works fine with commands.update.check set XXX: yes we want --merge and we passed that! + $ hg config commands.update.check + noconflict $ echo hi > bar $ echo bar >> bar + $ hg next + abort: conflicting changes + (do you want --merge?) + [255] $ hg next --merge merging bar warning: conflicts while merging bar! (edit, then use 'hg resolve --mark') @@ -460,6 +466,10 @@ Testing --merge works with other values of commands.update.check also XXX: things are broken! + $ hg prev --config commands.update.check=abort + abort: uncommitted changes + (do you want --merge?) + [255] $ hg prev --merge --config commands.update.check=abort file 'bar' was deleted in other [destination] but was modified in local [working copy]. What do you want to do? @@ -477,6 +487,10 @@ $ echo bar > bar $ hg add bar + $ hg next --config commands.update.check=abort + abort: uncommitted changes + (do you want --merge?) + [255] $ hg next --merge --config commands.update.check=abort merging bar warning: conflicts while merging bar! (edit, then use 'hg resolve --mark')