On Sat, Mar 29, 2008 at 12:48 PM, Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > On Sat, 29 Mar 2008, Paul wrote: > > > When I do a simple git-pull over SSH, why does it typically prompt me for my > > SSH password two or three times? And no, I am not inputting it wrong. > > In some versions of git, it makes separate connections to find out what > the remote's state is and to fetch the actual data. A third connection > should only be needed if there are new tags to fetch, and that would be > after some of the messages. > > One of the changes in the upcoming release is to reduce this to one, > except for an occasional second one. 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@xxxxxxxxxxxxxx's password: bd@xxxxxxxxxxxxxx'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@xxxxxxxxxxxxxx/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... -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
