D2100: infinitepush: delete the bundle2 part ordering related to pushrebase
pulkit (Pulkit Goyal)
phabricator at mercurial-scm.org
Fri Feb 9 11:45:56 UTC 2018
pulkit created this revision.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.
REVISION SUMMARY
pushrebase is another Facebook extension which does not live in core yet. So
let's remove the logic which make sures infinitepush part is moved before the
pushrebase one.
REPOSITORY
rHG Mercurial
REVISION DETAIL
https://phab.mercurial-scm.org/D2100
AFFECTED FILES
hgext/infinitepush/__init__.py
CHANGE DETAILS
diff --git a/hgext/infinitepush/__init__.py b/hgext/infinitepush/__init__.py
--- a/hgext/infinitepush/__init__.py
+++ b/hgext/infinitepush/__init__.py
@@ -190,7 +190,6 @@
default=False,
)
-pushrebaseparttype = 'b2x:rebase'
experimental = 'experimental'
configbookmark = 'server-bundlestore-bookmark'
configcreate = 'server-bundlestore-create'
@@ -365,12 +364,8 @@
wireproto.wirepeer.listkeyspatterns = listkeyspatterns
- # Move infinitepush part before pushrebase part
- # to avoid generation of both parts.
partorder = exchange.b2partsgenorder
index = partorder.index('changeset')
- if pushrebaseparttype in partorder:
- index = min(index, partorder.index(pushrebaseparttype))
partorder.insert(
index, partorder.pop(partorder.index(scratchbranchparttype)))
To: pulkit, #hg-reviewers
Cc: mercurial-devel
More information about the Mercurial-devel
mailing list