From: "Bryan Donlan" <bdonlan@gmail.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: Paul <lists@pote.com>, git@vger.kernel.org
Subject: Re: why multiple password prompts?
Date: Sun, 30 Mar 2008 18:05:05 -0400 [thread overview]
Message-ID: <3e8340490803301505y7df70787wad4449b1821e0d05@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0803301755200.19665@iabervon.org>
On Sun, Mar 30, 2008 at 5:56 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> On Sun, 30 Mar 2008, Bryan Donlan wrote:
>
> > git.git's master branch seems to be hitting ssh twice fairly reliably...
> > [bd@shion git-test] SSH_AUTH_SOCK= ~/src/git/git-pull
> > bd@130.111.246.25's password:
> > bd@130.111.246.25's password:
> > remote: Counting objects: 5, done.
> > remote: Compressing objects: 100% (2/2)remote: , done.
> > remote: Total 3 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (3/3), done.
> > From ssh+git://bd@130.111.246.25/home/bd/git-test
> > b0b8450..57a92a7 master -> origin/master
> > Updating b0b8450..57a92a7
> > Fast forward
> > fob | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> > [bd@shion git-test] ~/src/git/git --version
> > git version 1.5.5.rc2
> >
> > The remote's still on 1.5.4.4 if it matters...
>
> No, but ~/src/git/git-pull will run the installed git-fetch, not the
> locally built one, IIRC.
Ah, that would be it, thanks.
prev parent reply other threads:[~2008-03-30 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 15:44 why multiple password prompts? Paul
2008-03-29 16:48 ` Daniel Barkalow
2008-03-29 16:59 ` Jakub Narebski
2008-03-29 19:05 ` Daniel Barkalow
2008-03-29 18:37 ` Martin Langhoff
2008-03-29 18:49 ` Daniel Barkalow
2008-03-29 22:05 ` Jeff King
2008-03-29 22:11 ` Jeff King
2008-03-30 20:34 ` Bryan Donlan
2008-03-30 21:56 ` Daniel Barkalow
2008-03-30 22:05 ` Bryan Donlan [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=3e8340490803301505y7df70787wad4449b1821e0d05@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=lists@pote.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).