From: Sylvain Rabot <sylvain@abstraction.fr>
To: git@vger.kernel.org
Subject: Re: Minor bug in bash completion
Date: Wed, 30 Dec 2009 18:59:38 +0100 [thread overview]
Message-ID: <1262195978.3552.4.camel@kheops> (raw)
In-Reply-To: <20091230112222.GA493@neumann>
On Wed, 2009-12-30 at 12:22 +0100, SZEDER Gábor wrote:
> Hi Sylvain,
>
>
> On Tue, Dec 29, 2009 at 03:36:58PM +0100, Sylvain RABOT wrote:
> > I found a bug in the git bash completion.
> > It occurs when I press tab to complete branch name when I want to pull
> > from the origin.
> > Instead of completing the branch name it prompts me directly for my
> > password on the origin remote.
>
> I don't think it's a bug. The completion script should offer the
> currently available refs in the remote repository after a 'git pull
> <remote> <TAB>'. In order to do that it contacts the remote
> repository for the list of refs available there. Depending on the
> access method, it might need to authenticate, in your case via ssh.
> To silence the password prompts you should change your ssh
> configuration to use key-based authentication when logging in to the
> remote repository's server (just google for 'ssh login without
> password').
>
>
> Best,
> Gábor
Haaa,
I understand now, tough, I thought that the list of origin's branches
where stored somewhere in my local repository and that I needed to do a
"git remote update origin" to get the current origin branches list.
Thanks for your answer.
Regards.
--
Sylvain Rabot <sylvain@abstraction.fr>
next prev parent reply other threads:[~2009-12-30 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 14:36 Minor bug in bash completion Sylvain RABOT
2009-12-30 11:22 ` SZEDER Gábor
2009-12-30 17:59 ` Sylvain Rabot [this message]
2009-12-30 18:00 ` Junio C Hamano
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=1262195978.3552.4.camel@kheops \
--to=sylvain@abstraction.fr \
--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 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).