hg push with mq applied

[Bernd Schubert]

Robin Farine wrote:


> Should Hg replace change set 1 in A with the one in B or create a new
> head ? Or should mq redefine 'push' and 'pull' to cope with this
> situation ? What are the implications of each case ?

I'm presently busy patching and testing lustre, going all through this is
too difficult now ;)

> 
> To me, it seems easier and safer to never publish a repo with mq patches
> applied, but publish the patch series separately, perhaps as Gert
> suggests, by having the patch queue managed with Hg as well.

All I want is to push and pull the repository. If its not allowed to push it
with applied patches, fine, qpop is easy. However, the patches also should
be under a version control then and I would appreciate one single command
for pushing and pulling. Seems I have to implement what I need myself ;)

So far I used quilt for that purpose, unfortunately it somehow saves some
kind of status into the file permissions and removes all read and write
flags, hg then will complain about it, which also drives me crazy after the
100th time.

Bernd