Wed, 27 Aug 2014 17:09:36 +0200 obsexc: use the common discovery
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 17:09:36 +0200] rev 1078
obsexc: use the common discovery We drop the hand made discovery and rely on the general one introduced some time ago.
Wed, 27 Aug 2014 12:29:40 +0200 obsexc: push nothing if push fail
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 12:29:40 +0200] rev 1077
obsexc: push nothing if push fail This is closer to the future behavior with bundle2.
Fri, 29 Aug 2014 10:13:44 +0200 discovery: hook on the official discovery for obsmarker
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 29 Aug 2014 10:13:44 +0200] rev 1076
discovery: hook on the official discovery for obsmarker This will let the discovery be done once and used by core.
Wed, 27 Aug 2014 12:05:49 +0200 discovery: use a different setup step for discovery
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 12:05:49 +0200] rev 1075
discovery: use a different setup step for discovery This will ease the dropping of the other part later.
Wed, 27 Aug 2014 12:04:57 +0200 evolve: remove unused drop random
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 12:04:57 +0200] rev 1074
evolve: remove unused drop random
Wed, 27 Aug 2014 12:02:53 +0200 obshash: resist to unknown revision during discovery
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 12:02:53 +0200] rev 1073
obshash: resist to unknown revision during discovery
Wed, 27 Aug 2014 10:49:58 +0200 code movement: gather discovery code together
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 10:49:58 +0200] rev 1072
code movement: gather discovery code together The discovery code is the one thing that will survive the great purge.
Wed, 27 Aug 2014 10:53:09 +0200 bundle2: drop custom compat
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 10:53:09 +0200] rev 1071
bundle2: drop custom compat We'll rely on the core implementation to use bundle2.
Wed, 27 Aug 2014 10:22:50 +0200 drop relevant marker compat
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 10:22:50 +0200] rev 1070
drop relevant marker compat
Wed, 27 Aug 2014 10:21:30 +0200 evolve: always use the transaction version of phase movement
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 10:21:30 +0200] rev 1069
evolve: always use the transaction version of phase movement This drop compat with all known released version of Mercurial.
Wed, 27 Aug 2014 10:29:31 +0200 evolve: drop debugobsoleterelevant
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 27 Aug 2014 10:29:31 +0200] rev 1068
evolve: drop debugobsoleterelevant Core gained this capability usig `hg debugobsolete --rev REV`
Wed, 20 Aug 2014 20:49:48 -0700 evolve: yield to relevant markers handling in core
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 20 Aug 2014 20:49:48 -0700] rev 1067
evolve: yield to relevant markers handling in core The handling of obsolescence marker is now performed in core. If we detect a mercurial with such power we skip the wrapping from evolve. This changeset also suffer from massive diff from the change in display of obsolescence marker with parent information introduced at the same time in core.
Wed, 20 Aug 2014 21:14:49 -0700 test-wireproto: adapt to output change from core
Pierre-Yves David <pierre-yves.david@fb.com> [Wed, 20 Aug 2014 21:14:49 -0700] rev 1066
test-wireproto: adapt to output change from core
Fri, 15 Aug 2014 17:07:55 -0700 test: update test to new date formatting in debuobsolete output
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 15 Aug 2014 17:07:55 -0700] rev 1065
test: update test to new date formatting in debuobsolete output The date is now a first class citizen with proper formatting.
(0) -1000 -300 -100 -14 +14 +100 +300 +1000 +3000 tip