Always apply (and hide) some patches

[Danylo Hlynskyi]

Thanks, Rainer.

> I'm not quite sure whether your "secret commit WORKSPACE" really is part
> of your workfow  or whether it's rather  part of your solution for push-
> ing your development changesets upstream.

It is part of workflow, I don't want to push it.
----

I see, that MQ can be used instead of regular commits. But what I talk
about, is eliminate steps 2, 3, 5 and 7 from my workflow.

Actually, there is another way to do what I want.

0. make changes to workdir, which represent WORKSPACE commit, but never
commit them.
2. make actual bug/feature related changes, commit them. Workdir is dirty
with previous changes
3. push
4. commit subrepos

This looks ideal, except that `hg status` is always dirty. But it becomes
nightmare when
any history-modifying is involved - rebase, histedit, strip, backout.
Changes are to be
shelved/unshelved each time I have to do that. merge, graft, backout do
require
clean workdir, only `hg update` can automerge my changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20170606/0634eb25/attachment-0002.html>