evolve+amend+public: created a new head in bitbucket.

[Uwe Brauer]

Hi

Usually I am using only non publishing. Now I thought it would be a good
idea to make my bitbucket repo publishing.

The following happened.

    1. I have evolve enabled.

    2. I committed and pushed. The changeset became public.

    3. I realised that I forgot something. I changed the changeset to
       draft, amended a new commit and pushed.

Then hg log -G did not show anything unusual. 

In bitbucket I see however a new head (the changeset I pushed before the
amendment).

I see this changeset with

 hg log -G --hidden

So the question is. Could that scenario have been avoided?

The only option to get rid of the head in bitbucket is to strip it, via
bitbuckets interface. Is this correct? Is this a good practise. 
You shall I leave that head?

Regards

Uwe Brauer