Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:29:08 -0700] rev 21654
pull: split remote phases retrieval from actual application
We want to be able to retrieve phases information through bundle2. The logic to
apply remote phases will not change.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:02:51 -0700] rev 21653
wireproto: use pushkey.decodekey
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:00:20 -0700] rev 21652
pushkey: introduce an ``decodekeys`` function
This function provides a standardized way to exchange pushkey content over
the wire.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:00:08 -0700] rev 21651
wireproto: use pushkey.encodekey
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 14:57:28 -0700] rev 21650
pushkey: introduce an ``encodekeys`` function
This function provides a standardized way to exchange pushkey content over
the wire.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 13:44:16 -0700] rev 21649
bundle2: add more phase movement in the test
To test phase exchange with bundle2 we need some phase movement to happen.
Appropriate logging is added to track those changes.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 13:40:12 -0700] rev 21648
bundle2: use non-publishing repo in test
If we are going to test usage of bundle for phases exchange, we need some phase movements
to be exchanged.