Mon, 30 Jan 2012 17:46:15 +0100 phases: allow phase name in phases.new-commit settings stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 17:46:15 +0100] rev 16030
phases: allow phase name in phases.new-commit settings Before this commit only phase index where accepted
Mon, 30 Jan 2012 15:17:08 +0100 qfinish: do not set secret changeset to draft if mq.secret=false stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 15:17:08 +0100] rev 16029
qfinish: do not set secret changeset to draft if mq.secret=false If mq.secret=false, mq should not touch phase
Mon, 30 Jan 2012 17:39:05 +0100 mq: take mq.secret configuration into account when picking the default phase stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 17:39:05 +0100] rev 16028
mq: take mq.secret configuration into account when picking the default phase
Mon, 30 Jan 2012 17:37:45 +0100 qimport: when mq.secret=True set qimported revision as secret stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 17:37:45 +0100] rev 16027
qimport: when mq.secret=True set qimported revision as secret
Mon, 30 Jan 2012 17:36:30 +0100 qrefresh: keep changeset phase during refresh stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 17:36:30 +0100] rev 16026
qrefresh: keep changeset phase during refresh
Mon, 30 Jan 2012 17:33:09 +0100 phases: write default phase data as soon as possible. stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 17:33:09 +0100] rev 16025
phases: write default phase data as soon as possible. Marks phase data as dirty when computing default phase. Actual writing is done when the lock is released. So, read only operation don't write phase data because they don't lock the repo.
Mon, 30 Jan 2012 18:06:57 +0100 phase: accept old style revision specification stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 30 Jan 2012 18:06:57 +0100] rev 16024
phase: accept old style revision specification
Mon, 30 Jan 2012 11:32:09 -0600 push: return 1 if no changes found (issue3228) stable
Matt Mackall <mpm@selenic.com> [Mon, 30 Jan 2012 11:32:09 -0600] rev 16023
push: return 1 if no changes found (issue3228) Currently we have the following return codes if nothing is found: commit incoming outgoing pull push intended 1 1 1 1 1 documented 1 1 1 0 1 actual 1 1 1 0 0 This fixes the lower-right entry.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip