From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Junio C Hamano <gitster@pobox.com>
Cc: Hong Xu <xuhdev@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG] git bash-completion is incorrect for "git pull origin mas<tab>" if the ssh key is encrypted
Date: Thu, 22 Mar 2012 19:30:05 +0100 [thread overview]
Message-ID: <4F6B6FAD.6010905@in.waw.pl> (raw)
In-Reply-To: <vpqvclwo70a.fsf@bauges.imag.fr>
On 03/22/2012 06:55 PM, Matthieu Moy wrote:
> Junio C Hamano<gitster@pobox.com> writes:
>
>> Zbigniew Jędrzejewski-Szmek<zbyszek@in.waw.pl> writes:
>>
>>> Maybe git-ls-remote should learn --quiet?
>>
>> I would rather think that the completion should ask for refs only when
>> dealing with local repositories, without going over network, whether the
>> query involves authentication or not.
>
> It depends on what "network" is. When the network is just a machine on
> the same Gb-ethernet LAN, completion can still be useful (only if you
> have password-less authentication of course). I don't use it much with
> Git, but I find it handy that ZSH completes rsync remote pathes for
> example.
Yeah, I can second that. Even on a slow network, it can be useful. I use
ssh with ControlMaster=yes and completion over a relatively slow network
is pretty much instantaneous.
-
Zbyszek
next prev parent reply other threads:[~2012-03-22 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 6:04 [BUG] git bash-completion is incorrect for "git pull origin mas<tab>" if the ssh key is encrypted Hong Xu
2012-03-22 10:28 ` Zbigniew Jędrzejewski-Szmek
2012-03-22 12:10 ` Johannes Sixt
2012-03-22 12:48 ` Hong Xu
2012-03-22 12:55 ` Zbigniew Jędrzejewski-Szmek
2012-03-22 13:00 ` Hong Xu
2012-03-22 17:46 ` Junio C Hamano
2012-03-22 17:55 ` Matthieu Moy
2012-03-22 18:30 ` Zbigniew Jędrzejewski-Szmek [this message]
2012-03-22 18:45 ` Junio C Hamano
2012-03-22 17:56 ` Hong Xu
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=4F6B6FAD.6010905@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=xuhdev@gmail.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).