Tue, 17 Jan 2012 02:26:00 +0100 mq: qimporting revision set them to secret
Pierre-Yves David <pierre-yves.david@ens-lyon.org> [Tue, 17 Jan 2012 02:26:00 +0100] rev 15927
mq: qimporting revision set them to secret
Wed, 18 Jan 2012 16:53:49 +0100 mq: have mq create secret changeset only
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 18 Jan 2012 16:53:49 +0100] rev 15926
mq: have mq create secret changeset only
Wed, 18 Jan 2012 20:00:48 -0600 wireproto: refuse to lookup secret csets
Matt Mackall <mpm@selenic.com> [Wed, 18 Jan 2012 20:00:48 -0600] rev 15925
wireproto: refuse to lookup secret csets
Wed, 18 Jan 2012 19:16:01 -0600 qclone: ignore local qbase if secret
Matt Mackall <mpm@selenic.com> [Wed, 18 Jan 2012 19:16:01 -0600] rev 15924
qclone: ignore local qbase if secret
Wed, 18 Jan 2012 18:14:55 -0600 rebase: only advance phase on successful commit
Matt Mackall <mpm@selenic.com> [Wed, 18 Jan 2012 18:14:55 -0600] rev 15923
rebase: only advance phase on successful commit
Wed, 18 Jan 2012 17:23:54 +0100 phases: mechanism to allow extension to alter initial computation of phase
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 18 Jan 2012 17:23:54 +0100] rev 15922
phases: mechanism to allow extension to alter initial computation of phase This commit add a whennodata list where extension can register a callback to be called if no phase related data are found in the repository. The goal is to ensure the existing extension that move phase data in 2.1 can compute consistent phase boundary for existing repo.
Wed, 18 Jan 2012 17:11:27 +0100 qclone: add a few comment and blank line
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 18 Jan 2012 17:11:27 +0100] rev 15921
qclone: add a few comment and blank line This help readability.
Wed, 18 Jan 2012 17:06:59 +0100 mq: turn changeset draft on qfinish (except if qparent is secret)
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 18 Jan 2012 17:06:59 +0100] rev 15920
mq: turn changeset draft on qfinish (except if qparent is secret) As mq automatically sets changesets as secret, it should make them draft when he is done with it. We do not move them automatically to draft when we detect that something else have also set them as secret through their parents.
Wed, 18 Jan 2012 16:52:26 +0100 config: have a way to backup and restore value in config
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 18 Jan 2012 16:52:26 +0100] rev 15919
config: have a way to backup and restore value in config This is introduce to allow temporary overwriting of a config value while being able to reinstall the old value once done. The main advantage over using ``config`` and ``setconfig`` is that backup and restore will properly restore the lack of any config. Restoring the fact that there was no value is important to allow config user to keep using meaniful default value. A more naive approach will result in the following scenario:: Before: config(section, item, my_default) --> my_default temporal overwrite old = config(section, item) … setconfig(section, item, old) After config(section, item, my_default) --> None The first user of this feature should be mq to overwriting minimal phase of future commit.
Tue, 17 Jan 2012 11:08:23 +0100 graft: add test to check the phase of new changesets
Alain Leufroy <alain.leufroy@logilab.fr> [Tue, 17 Jan 2012 11:08:23 +0100] rev 15918
graft: add test to check the phase of new changesets Graft actually do not keep the phase of the source changesets: no need to change the graft code and add test to check this behaviour.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip