Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:17:05 -0500] rev 21685
memctx: remove extra since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:14:47 -0500] rev 21684
memctx: remove branch since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Wed, 28 May 2014 20:03:38 -0500] rev 21683
memctx: remove clean since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Wed, 28 May 2014 20:03:29 -0500] rev 21682
memctx: remove ignored since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Wed, 28 May 2014 20:03:19 -0500] rev 21681
memctx: remove unknown since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:13:14 -0500] rev 21680
memctx: remove deleted since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:12:54 -0500] rev 21679
memctx: remove removed since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:12:46 -0500] rev 21678
memctx: remove added since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:12:31 -0500] rev 21677
memctx: remove modified since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:12:19 -0500] rev 21676
memctx: remove files since it is now inherited
This is a slight change in definition from memctx returning only modified() but
its parent's definition is more consistent with other contexts' behavior so we
can call this change a slight bugfix and step in the right direction.
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:07:43 -0500] rev 21675
memctx: remove description since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:07:29 -0500] rev 21674
memctx: remove date since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:07:01 -0500] rev 21673
memctx: remove user since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:06:39 -0500] rev 21672
memctx: remove p2 since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:06:10 -0500] rev 21671
memctx: remove p1 since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:05:32 -0500] rev 21670
memctx: remove __getitem__ since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:04:55 -0500] rev 21669
memctx: remove __nonzero__ since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:04:36 -0500] rev 21668
memctx: remove __int__ since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:03:52 -0500] rev 21667
memctx: remove __str__ since it is now inherited
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:03:03 -0500] rev 21666
memctx: call super.__init__ instead of duplicating code
Sean Farley <sean.michael.farley@gmail.com> [Thu, 15 Aug 2013 15:00:03 -0500] rev 21665
memctx: inherit from committablectx
This patch marks the start of having memctx inherit from committablectx,
thereby making it a full-fledged context that will eventually grow the ability
to perform diffing and also merging.
Sean Farley <sean.michael.farley@gmail.com> [Tue, 29 Apr 2014 16:49:27 -0500] rev 21664
committablectx: fix _manifest doc string
Sean Farley <sean.michael.farley@gmail.com> [Thu, 29 May 2014 16:09:16 -0500] rev 21663
context: fix wrong indentation from renaming method
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 16:33:06 -0700] rev 21662
push: use bundle2 to push phases when available
We now use a bundle2 container to push all phase updates at the same time. This
is a significant step forward, even if further refactoring is needed to unify
phase push with the changeset push.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 29 May 2014 15:22:58 -0700] rev 21661
pushkey: add an ``encode`` function
This function is just a shorthand for ``encoding.fromlocal``. It will help
hiding the encoding business from other code exchanging pushkey data over the
wire.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 16:32:50 -0700] rev 21660
bundle2: add ``pushkey`` support
After ``listkeys`` we can now include ``pushkey`` request in a bundle2. The part
uses a very simple scheme closest as possible to the current wireproto command
for ``pushkey``. We may eventually decide for a more sophisticated part format
before the protocol becomes final.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 29 May 2014 15:23:25 -0700] rev 21659
pushkey: add a ``decode`` function
This function is just a shorthand for ``decoding.fromlocal``. It will help
hiding the encoding business from other code exchanging pushkey data over the
wire.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:44:46 -0700] rev 21658
pull: when remote supports it, pull phase data alongside changesets
We use bundle2 to retrieve the remote phase data at the same time as
changesets. This reduces the amount of requestis and should improve consistency
as the server can ensure nothing changed between the retrieval of those parts.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 15:43:09 -0700] rev 21657
getbundle: support of listkeys argument when bundle2 is used
A new ``listkeys`` is supported by getbundle. It is a list of namespaces whose
content should be included in the bundle.
An appropriate entry has been added to the wireproto map of getbundle arguments
and a new bundle2 capability is advertised.
There are still no codes that request such parts in core mercurial.
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 29 May 2014 14:59:22 -0700] rev 21656
getbundle: raise error if extra arguments are provided for bundle10
New arguments are most likely to be supported by bundle20 (and above) only.