Mercurial > hg > mercurial-source
changeset 37982:14acab54e08b
infinitepush: drop hack related to --to, --create flags of remotenames-ext
The remotenames extension has --to, --create. --allow-anon flags which won't be
ported to core. This patch drops the hack which fixes the interaction with
remotenames-ext during push.
In upcoming patches, --to and --create extensions will be removed from
infinitepush also.
Differential Revision: https://phab.mercurial-scm.org/D2105
author | Pulkit Goyal <7895pulkit@gmail.com> |
---|---|
date | Fri, 09 Feb 2018 13:56:09 +0530 |
parents | 3be6f435db4f |
children | 7fa00a6f8180 |
files | hgext/infinitepush/__init__.py |
diffstat | 1 files changed, 0 insertions(+), 10 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/infinitepush/__init__.py +++ b/hgext/infinitepush/__init__.py @@ -771,16 +771,6 @@ with ui.configoverride(overrides, 'infinitepush'): scratchpush = opts.get('bundle_store') if _scratchbranchmatcher(bookmark): - # Hack to fix interaction with remotenames. Remotenames push - # '--to' bookmark to the server but we don't want to push scratch - # bookmark to the server. Let's delete '--to' and '--create' and - # also set allow_anon to True (because if --to is not set - # remotenames will think that we are pushing anonymoush head) - if 'to' in opts: - del opts['to'] - if 'create' in opts: - del opts['create'] - opts['allow_anon'] = True scratchpush = True # bundle2 can be sent back after push (for example, bundle2 # containing `pushkey` part to update bookmarks)