did evolve+histedit screw up some changesets??

[Uwe Brauer]

Hi

I am on Ubuntu 16.04, running 

Hg 5.2rc0+20200125
and evolve change set 3f9ef377e670

Now 

    - I run hg histedit on a change set (since I did not like its commit message),

    - I did not like the new change set neither, so

    - hg uncommit -a 

Now the graph looks like 


  changeset:   56:2b273979d636
│  Branch:      default
│  tag:         tip
│  Author:      Uwe Brauer <oub at mat.ucm.es>
│  Date:        Wed, 10 Aug 2022 17:13:45 +0200
│  Phase:       draft
│  Summary:     Set up the exterior files, so that they can be compiled. Solve markup questions
│
∗  changeset:   55:8d95b4026b39
│  Branch:      default
│  Author:      Uwe Brauer <oub at mat.ucm.es>
│  Date:        Wed, 10 Aug 2022 17:12:34 +0200
│  Phase:       draft
│  Summary:     Clarify integration by parts
│
◌  changeset:   54:979c8bfa9c35
│  Branch:      default
│  Author:      Uwe Brauer <oub at mat.ucm.es>
│  Date:        Wed, 10 Aug 2022 17:11:28 +0200
│  Phase:       draft
│  Summary:     2022-08-10  Uwe Brauer  <oub at mat.ucm.es>


When I want to checkout change set 54 I obtain 

5 files updated, 0 files merged, 1 files removed, 0 files unresolved
working directory parent is obsolete! (979c8bfa9c35)
(use 'hg evolve' to update to its parent successor)


I don't understand why this change set is obsolete, I thought 

 hg commit -a
 hg prune .

Would not make that change set obsolete (maybe I should have used strip
instead of hg commit -a, but it is a draft change set anyhow)

Any idea how to proceed.

Is this harmful?

Uwe Brauer 

-- 
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.