From: Junio C Hamano <gitster@pobox.com>
To: William Giokas <1007380@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] remote-hg: getbundle changed in mercurial 3.0
Date: Tue, 13 May 2014 14:00:18 -0700 [thread overview]
Message-ID: <xmqqmwelmm1p.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1400012506-20705-1-git-send-email-1007380@gmail.com> (William Giokas's message of "Tue, 13 May 2014 15:21:46 -0500")
William Giokas <1007380@gmail.com> writes:
> +try:
> + from mercurial.changegroup import getbundle
> +
> +except ImportError:
> + def getbundle(repo, **kwargs):
> + return repo.getbundle(**kwargs)
> +
> import re
> import sys
> import os
> @@ -985,7 +992,8 @@ def push_unsafe(repo, remote, parsed_refs, p_revs):
> if not checkheads(repo, remote, p_revs):
> return None
>
> - cg = repo.getbundle('push', heads=list(p_revs), common=common)
> + cg = getbundle(repo=repo, source='push', heads=list(p_revs),
> + common=common)
Yikes, this is starting to look bad, but the thing being in Python,
perhaps that is the best we could do if we want a solution that is
viable in the longer term.
As a short-term band-aid to be merged/cherry-picked to maintenance
tracks post 2.0 final, I actually would prefer 58aee086 (remote-hg:
add support for hg v3.0, 2014-05-03) for its simplicity.
I dunno. Thankfully I do not have to decide right now ;-)
next prev parent reply other threads:[~2014-05-13 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 19:12 [PATCH] remote-hg: getbundle changed in mercurial 3.0 William Giokas
2014-05-13 20:21 ` [PATCH v2] " William Giokas
2014-05-13 21:00 ` Junio C Hamano [this message]
2014-05-13 20:33 ` [PATCH] " Junio C Hamano
2014-05-13 20:59 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmwelmm1p.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=1007380@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.