[2.1 CHANGES] MQ behavior regarding phases
L. David Baron
dbaron at dbaron.org
Thu Jan 26 00:50:41 UTC 2012
On Wednesday 2012-01-25 22:52 +0100, Pierre-Yves David wrote:
> 1) mq.secret=false
> ------------------
>
>
> qnew: create draft changeset
>
> qrefresh: keep the changeset in the phase it were.
> * draft changeset is refreshed as draft
> * secret changeset is refreshed as secret
>
> qimport: don't touch the changeset phases
>
> qpush: push patches as draft (so beware that a qpop/qpush patch may turn secret
> changeset draft)
>
> Mercurial will see mq patches as draft the first time it touch an old repository
>
> As mercurial make a lot of effort to stay backward compatible, this is the
> default behavior. This is sad but necessary. People who want a safe mq should
> set mq.secret=true.
This option sounds like it should solve my problems; thanks.
Assuming it does, that's the case whether or not it's the default
value. And I may well be an unusual enough user that it's ok for me
to have to set a new option when upgrading, though it looks like mpm
thinks otherwise.
-David
--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla http://www.mozilla.org/ 𝄂
More information about the Mercurial-devel
mailing list