(corrupt repo, repaired) pushing remote has heads on branch 'default' that are not known locally

[Uwe Brauer]

    > On Mon, Jul 25, 2016 at 9:13 AM, Uwe Brauer <oub at mat.ucm.es> wrote:


    > How you resolve this depends on what you use the bitbucket
    > repository for. If it is just for personal use, perhaps as a
    > backup, then I would probably rename the bitbucket repository and
    > create a new empty one in its place. Then you can push the results
    > of the conversion to the new empty repository. (The renamed one
    > can be deleted once you are *completely certain* that you don't
    > need anything from it).

Ok, this is the case (private repo/backup) and your proposal is the
solution I was thinking about.

However I have also repos which I share for collaboration (fortunately I
had no data corruption so far). What should I do in such a case? Better
not use the convert extension?

What is about repos I use with the git-hg plugin, any rule how to deal
with data corruption in those cases?




    > Hope that helps,

it does, as always.

thanks

Uwe