Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:42:03 -0700] rev 21655
bundle: introduce a listkey handler
This makes it possible to handle listkeys-related data stored in a bundle2.
There are no producers yet.
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.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 13:30:38 -0700] rev 21647
bundle2: use a smarter template for test
We use a more compact template that includes phase information.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 22 May 2014 09:53:52 -0700] rev 21646
getbundle: declare type of parameters
In addition to listing the expected options for ``getbundle``, we also list their
types and handle the encoding/decoding automatically. This should make it easier
for extensions to transmit additional information to getbundle.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 22 May 2014 13:31:33 -0700] rev 21645
bundle2: introduce a ``caps20to10`` function
This function factors the creation of appropriate entries to use in
``bundlecaps`` argument of ``getbundle``. This cleans up code calling
``getbundle`` and helps its usage in more part of the code.
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 24 May 2014 16:20:09 -0700] rev 21644
bundle2: introduce a bundle2caps function
The process of decoding remote bundle2caps blob into a dictionary is cumbersome.
We move it into a small helper function. This will clarify code that reads
bundle2 capabilities of peers and helps using it in new places.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 22 May 2014 12:58:07 -0700] rev 21643
exchange: reinsert comment in the right place
Unrelated new code was inserted between the original comment and the related
code block.
Matt Mackall <mpm@selenic.com> [Thu, 29 May 2014 16:01:39 -0700] rev 21642
docker: check for docker.io first
Mads Kiilerich <madski@unity3d.com> [Tue, 20 May 2014 04:07:58 +0200] rev 21641
buildrpm: include release version in .tar.gz name
Official releases are fully indentified by the version number, these builds are
not.
Specs are however traditionally not versioned.