From: Felipe Contreras <felipe.contreras@gmail.com>
To: Richard Hansen <rhansen@bbn.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] remote-bzr: reuse bzrlib transports when possible
Date: Sat, 7 Sep 2013 19:27:42 -0500 [thread overview]
Message-ID: <CAMP44s3Vw4GX+yL22F49uKFZcEvYmXC7nT9TCGW_jybhFHo1Og@mail.gmail.com> (raw)
In-Reply-To: <1378598300-22737-1-git-send-email-rhansen@bbn.com>
On Sat, Sep 7, 2013 at 6:58 PM, Richard Hansen <rhansen@bbn.com> wrote:
> Pass a list of open bzrlib.transport.Transport objects to each bzrlib
> function that might create a transport. This enables bzrlib to reuse
> existing transports when possible, avoiding multiple concurrent
> connections to the same remote server.
>
> If the remote server is accessed via ssh, this fixes a couple of
> problems:
> * If the user does not have keys loaded into an ssh agent, the user
> may be prompted for a password multiple times.
> * If the user is using OpenSSH and the ControlMaster setting is set
> to auto, git-remote-bzr might hang. This is because bzrlib closes
> the multiple ssh sessions in an undefined order and might try to
> close the master ssh session before the other sessions. The
> master ssh process will not exit until the other sessions have
> exited, causing a deadlock. (The ssh sessions are closed in an
> undefined order because bzrlib relies on the Python garbage
> collector to trigger ssh session termination.)
Looks good to me. I'll apply in my personal repository.
--
Felipe Contreras
prev parent reply other threads:[~2013-09-08 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 23:58 [PATCH] remote-bzr: reuse bzrlib transports when possible Richard Hansen
2013-09-08 0:02 ` Richard Hansen
2013-09-08 0:30 ` Felipe Contreras
2013-09-08 5:30 ` Richard Hansen
2013-09-08 5:47 ` [PATCH v2] " Richard Hansen
2013-09-09 17:55 ` Junio C Hamano
2013-09-10 22:01 ` Junio C Hamano
2013-09-12 21:05 ` Richard Hansen
2013-09-12 21:11 ` Junio C Hamano
2013-09-08 0:27 ` Felipe Contreras [this message]
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=CAMP44s3Vw4GX+yL22F49uKFZcEvYmXC7nT9TCGW_jybhFHo1Og@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rhansen@bbn.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).