Tue, 03 Jun 2014 14:31:15 -0700 merge stable into default
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 03 Jun 2014 14:31:15 -0700] rev 968
merge stable into default default is meant to be a superset of stable
Tue, 03 Jun 2014 14:30:23 -0700 merge default in to stable stable
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 03 Jun 2014 14:30:23 -0700] rev 967
merge default in to stable evolve 4.0.0 is coming.
Tue, 03 Jun 2014 14:29:24 -0700 merge back into stable stable
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 03 Jun 2014 14:29:24 -0700] rev 966
merge back into stable The 2,7 is meant to be a subset of stable.
Tue, 03 Jun 2014 14:28:31 -0700 prepare a branch for compatibility with mercurial 2.7 to 3.0(.0) mercurial-2.7
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 03 Jun 2014 14:28:31 -0700] rev 965
prepare a branch for compatibility with mercurial 2.7 to 3.0(.0) Evolve 4.0.0 is coming
Mon, 02 Jun 2014 15:22:23 -0700 test: update to output change introduced by future 3.1
Pierre-Yves David <pierre-yves.david@fb.com> [Mon, 02 Jun 2014 15:22:23 -0700] rev 964
test: update to output change introduced by future 3.1
Wed, 21 May 2014 12:01:28 -0700 simple4server: backport the bundle2 exchange
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 21 May 2014 12:01:28 -0700] rev 963
simple4server: backport the bundle2 exchange
Tue, 20 May 2014 22:36:47 -0700 evolve: install progress support for the bundle2 pull path
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 20 May 2014 22:36:47 -0700] rev 962
evolve: install progress support for the bundle2 pull path The custom wireprotocol command had a trick to display progress while pulling. We reinstall such logic for the new path using bundle2. Its notable that we are using the bundle2 advisory parameter for this purpose.
Tue, 20 May 2014 17:21:36 -0700 evolve: install progress support for the bundle2 push path
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 20 May 2014 17:21:36 -0700] rev 961
evolve: install progress support for the bundle2 push path The custom wireprotocol command had a trick to display progress while pushing. We reinstall such logic for the new path using bundle2.
Tue, 20 May 2014 14:39:13 -0700 evolve: add a pull path using bundle2
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 20 May 2014 14:39:13 -0700] rev 960
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.
Tue, 03 Jun 2014 02:13:02 -0700 evolve: advertise obsmarker creation in the transation hook
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 03 Jun 2014 02:13:02 -0700] rev 959
evolve: advertise obsmarker creation in the transation hook This will let extensions hooks on marker exchange.
(0) -300 -100 -10 +10 +100 +300 +1000 +3000 tip