Mercurial > evolve
comparison tests/test-prev-next.t @ 3812:25dfa95c37fd stable
next-prev: add tests showing --merge not respected in some cases
This patch adds tests which show that --merge is not respected when you set
commands.update.check to any value.
This is a bug I wrote few days ago and will fix it in next changeset.
I like this process of writing bugs and fixing them.
author | Pulkit Goyal <7895pulkit@gmail.com> |
---|---|
date | Fri, 08 Jun 2018 18:32:48 +0530 |
parents | 838fc71ddb9c |
children | 27e7ed2d13a6 |
comparison
equal
deleted
inserted
replaced
3793:3343c5491b31 | 3812:25dfa95c37fd |
---|---|
437 | 437 |
438 $ hg next | 438 $ hg next |
439 abort: conflicting changes | 439 abort: conflicting changes |
440 (do you want --merge?) | 440 (do you want --merge?) |
441 [255] | 441 [255] |
442 | |
443 Test that --merge still works fine with commands.update.check set | |
444 | |
445 XXX: yes we want --merge and we passed that! | |
446 $ echo hi > bar | |
447 $ echo bar >> bar | |
448 $ hg next --merge | |
449 abort: conflicting changes | |
450 (do you want --merge?) | |
451 [255] | |
452 | |
453 Testing --merge works with other values of commands.update.check also | |
454 | |
455 XXX: things are broken! | |
456 $ hg prev --merge --config commands.update.check=abort | |
457 abort: uncommitted changes | |
458 (do you want --merge?) | |
459 [255] | |
460 | |
461 $ hg revert --all | |
462 forgetting bar | |
463 reverting wat | |
464 | |
465 $ echo bar > bar | |
466 $ hg add bar | |
467 | |
468 $ hg next --merge --config commands.update.check=abort | |
469 abort: uncommitted changes | |
470 (do you want --merge?) | |
471 [255] |