touch: prompt the user for what to do with the revived changeset
This patch improves our interface for reviving changesets.
This patch makes touch not assume that the user wants to create divergence by
default and gives a prompt instead. The prompt is skipped for changeset that
have no living successor as no divergence would be created by reviving them
anyway.
To restore the previous behavior, one should now use the --allowdivergence flag.
The prompt looks like:
[10] <description>
reviving this changeset will create divergence unless you make a duplicate.
(a)llow divergence or (d)uplicate the changeset? a
In further patches we will want to add one more choice to that prompt, for
example having a marker between the old and revived nodes but no divergence
displayed on the UI.
mercurial-evolve (5.2.1-1) unstable; urgency=medium
* New upstream release.
-- Faheem Mitha <faheem@faheem.info> Wed, 30 Dec 2015 03:46:06 +0530
mercurial-evolve (5.2.0-1) unstable; urgency=medium
* New upstream release.
-- Pierre-Yves David <pierre-yves.david@ens-lyon.org> Thu, 25 Jun 2015 17:41:56 -0700
mercurial-evolve (5.1.3-1) unstable; urgency=medium
* new upstream release
-- Julien Cristau <julien.cristau@logilab.fr> Mon, 20 Apr 2015 14:44:45 +0200
mercurial-evolve (5.0.2-1) unstable; urgency=medium
* new upstream release
-- Pierre-Yves David <pierre-yves.david@ens-lyon.org> Sun, 14 Dec 2014 12:43:28 -0800
mercurial-evolve (5.0.1-1) unstable; urgency=medium
* New upstream release.
-- Faheem Mitha <faheem@faheem.info> Wed, 12 Nov 2014 11:24:28 +0530
mercurial-evolve (5.0.0+-1) UNRELEASED; urgency=low
* new upstream snapshot
-- Julien Cristau <julien.cristau@logilab.fr> Mon, 17 Nov 2014 15:44:32 +0100
mercurial-evolve (4.1.0-1) unstable; urgency=medium
* new upstream release
-- Pierre-Yves David <pyd@marginatus.alto.octopoid.net> Fri, 08 Aug 2014 23:15:11 -0700
mercurial-evolve (4.0.1-1) unstable; urgency=medium
* new upstream release
-- Pierre-Yves David <pyd@marginatus.alto.octopoid.net> Fri, 08 Aug 2014 15:50:09 -0700
mercurial-evolve (4.0.0-1) unstable; urgency=low
[ Julien Cristau ]
* New upstream release.
[ Pierre-Yves David ]
* new upstream release
-- Pierre-Yves David <pyd@marginatus.alto.octopoid.net> Fri, 08 Aug 2014 15:48:16 -0700
mercurial-evolve (3.1.0-1) UNRELEASED; urgency=low
* New upstream release.
-- Pierre-Yves David <pierre-yves.david@logilab.fr> Mon, 04 Mar 2013 18:02:15 +0100
mercurial-evolve (2.1.0-1) UNRELEASED; urgency=low
* New upstream release
-- Pierre-Yves David <pierre-yves.david@logilab.fr> Mon, 03 Dec 2012 15:19:19 +0100
mercurial-evolve (1.1.0-1) UNRELEASED; urgency=low
* New upstream release.
-- Pierre-Yves David <pierre-yves.david@logilab.fr> Tue, 20 Nov 2012 16:28:12 +0100
mercurial-evolve (1.0.2-1) UNRELEASED; urgency=low
* New upstream Release
-- Pierre-Yves David <pierre-yves.david@logilab.fr> Wed, 19 Sep 2012 17:38:47 +0200
mercurial-evolve (1.0.1-1) UNRELEASED; urgency=low
* New bug fix release
* remove conflicting __init__.py
-- Pierre-Yves David <pierre-yves.david@logilab.fr> Fri, 31 Aug 2012 11:31:03 +0200
mercurial-evolve (1.0.0-1) UNRELEASED; urgency=low
* Initial release.
-- Julien Cristau <jcristau@debian.org> Fri, 24 Aug 2012 16:46:30 +0200