From: Jeff King <peff@peff.net>
To: Neal Groothuis <ngroot@lo-cal.org>
Cc: Feanil Patel <feanil@gmail.com>, git@vger.kernel.org
Subject: Re: Push from an SSH Terminal
Date: Fri, 3 Feb 2012 16:36:55 -0500 [thread overview]
Message-ID: <20120203213654.GD1890@sigill.intra.peff.net> (raw)
In-Reply-To: <34592.38.96.167.131.1328289027.squirrel@mail.lo-cal.org>
On Fri, Feb 03, 2012 at 12:10:27PM -0500, Neal Groothuis wrote:
> > On Fri, Feb 3, 2012 at 11:21 AM, Neal Groothuis <ngroot@lo-cal.org> wrote:
> >>> The
> >>> repository is password protected so if I'm physically at Comp B, I get
> >>> a gui prompt for my username and password. However Comp A does not
> >>> have X Forwarding setup to Comp B so I can't get the gui interface for
> >>> the username and password when I try to do the push. Â Is there an
> >>> alternative way to provide my credentials when doing a git push that
> >>> does not require a gui?
> >>
> >> What protocol are you using to access the repository on Comp C?
> >>
> > I'm pulling and pushing over HTTP from Comp C.
>
> Check to see if the GIT_ASKPASS and/or SSH_ASKPASS environment variables
> are set, and if the core.askpass config variable is set. If any of these
> are set, unset them. Git should fall back to a simple password prompt.
Hmm, yeah that is likely the problem. I was thinking git would fall back
to asking on the terminal, but it does not. We probably should.
-Peff
next prev parent reply other threads:[~2012-02-03 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:50 Push from an SSH Terminal Feanil Patel
2012-02-03 16:21 ` Neal Groothuis
2012-02-03 16:40 ` Feanil Patel
2012-02-03 17:10 ` Neal Groothuis
2012-02-03 21:36 ` Jeff King [this message]
2012-02-03 22:13 ` Jeff King
2012-02-03 22:14 ` [PATCH 1/2] prompt: clean up strbuf usage Jeff King
2012-02-03 22:16 ` [PATCH 2/2] prompt: fall back to terminal if askpass fails Jeff King
2012-02-04 7:47 ` Push from an SSH Terminal Junio C Hamano
2012-02-04 8:09 ` Jeff King
2012-02-04 8:16 ` Junio C Hamano
2012-02-03 21:35 ` Jeff King
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=20120203213654.GD1890@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=feanil@gmail.com \
--cc=git@vger.kernel.org \
--cc=ngroot@lo-cal.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).