Adding phase support to TortoiseHG
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Sun Jan 22 03:59:34 CST 2012
On 22 janv. 2012, at 02:03, Angel Ezquerra wrote:
> I have a few more questions:
> - do mq patches have phase information? If not, should they be
> considered draft or secret?
applied mq patch have phase information: they are secret in simple case.
unapplied mq patches do not hold patches information but will be applied
as secret.
* mq are qnew'ed as secret
* mq are qpush'ed as secret
* qrefresh result are secret
But, you can change the phase of an mq patche to draft (or event public!)
eg: revision are qimported in the phase they are.
> - is the list of phase names publicly available in some accessible
> list? I must show the list of phases in order to let the user change
> the phase from the guy, but I'd rather not hard code the different
> phase names
mercurial.phases.phasenames
> - is there an easy way to tell if we are trying to move the phase
> backward? I'd like to warn the user and ask him if he wants to force
> the phase change in that case. Since there are only 3 phases I could
> simply take all possible cases into account, but I'd rather use a more
> general solution, in case new phases are added in the future.
mercurial.phases.allphases hold the numerical value of phases. You are
moving it backward when::
dest-phase > orig-phase
Moreover, you have to use different function to move phase in both direction.
so you can not more phase backward by mistake is you use advanceboundary.
See the phase command for details
More information about the Mercurial-devel
mailing list