From: Petr Baudis <pasky@suse.cz>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: Calling ssh from git-gui
Date: Wed, 3 Sep 2008 19:33:10 +0200 [thread overview]
Message-ID: <20080903173310.GY10360@machine.or.cz> (raw)
In-Reply-To: <20080903171543.GC28315@spearce.org>
On Wed, Sep 03, 2008 at 10:15:43AM -0700, Shawn O. Pearce wrote:
> And that is why it doesn't handle (ii) or (iii) at the present time,
> and unless I am given a nice patch series for any git-gui related
> parts of this, why it will continue to remain that way for quite
> some time.
My writeup was not actually intended as 'how we might do it' but 'how
should *I* implement this'. ;-) I _do_ plan for a nice patch series.
For now I'm defaulting on the SSH_ASKPASS approach.
> Damn annoying for git-gui to be invoking a new terminal window, but
> maybe that's what we have to do. Be nice though if the window only
> was opened because we couldn't do "git ls-remote url" but its hard
> to tell "hanging because SSH needs the user" and "hanging because
> the network is a 2400 baud modem".
Oh, indeed - that is something what I had in mind when starting to write
this mail about a week ago, but forgot to mention now. It's the
possibility of having console spawn a real tty (or do some more stuff to
*emulate* a tty, but again, this might get hairy in TCL). However, this
feels very... "untidy" compared to SSH_ASKPASS.
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
prev parent reply other threads:[~2008-09-03 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 16:54 Calling ssh from git-gui Petr Baudis
2008-09-03 17:15 ` Shawn O. Pearce
2008-09-03 17:22 ` Thomas Rast
2008-09-03 17:25 ` Shawn O. Pearce
2008-09-03 17:33 ` Petr Baudis [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=20080903173310.GY10360@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.