comparison tests/test-prune.t @ 4702:fcecbb1261f2 stable

evolve: fix the inconsistent behaviour of prune (issue6137) Let's not update to any revision when working directory parent is not related to the revision being pruned. Changes in test file demonstrate the fixed behaviour.
author Sushil khanchi <sushilkhanchi97@gmail.com>
date Mon, 01 Jul 2019 19:15:57 +0530
parents 1b5da965d72a
children c6fc1000af1e 6c02b9ac2832
comparison
equal deleted inserted replaced
4701:1b5da965d72a 4702:fcecbb1261f2
491 | @ 1:5f6d8a4bf34a[] (obsolete/draft) added b 491 | @ 1:5f6d8a4bf34a[] (obsolete/draft) added b
492 |/ 492 |/
493 o 0:9092f1db7931[] (draft) added a 493 o 0:9092f1db7931[] (draft) added a
494 494
495 $ hg prune -r "desc('added c')" 495 $ hg prune -r "desc('added c')"
496 0 files updated, 0 files merged, 1 files removed, 0 files unresolved
497 working directory is now at 9092f1db7931
498 1 changesets pruned 496 1 changesets pruned
499 497
500 $ hg par 498 $ hg par
501 0:9092f1db7931[] (draft) added a 499 1:5f6d8a4bf34a[] (obsolete/draft) added b
502 XXX: it doesn't make sense to update to "added a"; parent should be "added b" 500 working directory parent is obsolete! (5f6d8a4bf34a)
501 (use 'hg evolve' to update to its parent successor)
503 502
504 $ cd .. 503 $ cd ..