hg-git: push -d default seems not to work.

[Uwe Brauer]

    > On Fri, 12 May 2017 11:21:16 -0400, Uwe Brauer <oub at mat.ucm.es> wrote:

    > What I was getting at is, while it's possible, it doesn't make sense
    > to commit there. I can't think of any time I've ever updated to a
    > hidden commit. (Or other command for that matter, other than to
    > extdiff against a successor.)

But what are you doing if your patch is rejected?
I mean, you suggested.

hg branch -q feature
hack hack
hg update default
hg pull -u
hg rebase -d . -b feature --collapse

Then either push or send a patch.

But if the patch is rejected? That is most of the time my scenario I
mean in one repo I push (and it is usually accepted) but in another I 
export and send a patch and wait for feedback, if accepted fine. But if
not then I would strip the last commit, and checkout the latest (hidden)
commit of the feature branch,
hack hack correct 

And repeat the process above. But that seems not what you are doing.
Besides if I push, that later on I could not rebase because the pushed
commit is public.

So I would appreciate if you can tell me what you do if your patch is
rejected or modified.
Thanks

Uwe