evolve: add a pull path using bundle2
Instead of using a dedicated wireprotocol commands, we use bundle2 to transmit
an obs marker parts. This aims at both testing bundle2 more and to limit the
amount of special code we needs to put in simple for server to fit our needs.
The massive test changes comes from the fact we can use this fast path for both
remote and local push.
mercurial-evolve (3.2.0-1) UNRELEASED; urgency=low
* New upstream release.
-- Julien Cristau <julien.cristau@logilab.fr> Tue, 04 Jun 2013 17:28:02 +0200
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