hg push with mq applied

[solo turn]

i m just wondering what would be the solution if you would have to
design the command workflow from scratch to be the most simple /
practical one (no reference to existing commands and mq necessary)?

On 5/25/07, Eric M. Hopper <hopper at omnifarious.org> wrote:
> > If you really want to force it, push -r will allow you to push with mq
> > patches applied. But it's much better to version .hg/patches. You can
> > set up a trivial hook to push .hg/patches when you push the main
> > repository.
>
> I think this isn't what he wants to do.  I think what he wants is for
> push to push both the repo (if any) that contains the MQ patches and the
> main repo at the same time.  I can quite understand this desire as I've
> had it many times myself.
>
> If you use hg qinit, it puts the mq patches under version control in
> their own separate repository.  You can then use qcommit to commit
> changes to that repo, which happen when you add a new patch or modify an
> existing one with qrefresh.  It explicitly doesn't put the list of
> currently applied patches under version control as that would just be
> silly.
>
> Have fun (if at all possible),
> --
> The best we can hope for concerning the people at large is that they
> be properly armed.  -- Alexander Hamilton
> -- Eric Hopper (hopper at omnifarious.org  http://www.omnifarious.org/~hopper) --
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>
>