From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Edward Z. Yang" <edwardzyang@thewritingpot.com>
Cc: git@vger.kernel.org, gitster@pobox.com,
msysGit <msysgit@googlegroups.com>,
junio@pobox.com
Subject: Re: [PATCH 06/12] connect: Fix custom ports with plink (Putty's ssh)
Date: Thu, 3 Jul 2008 13:29:27 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807031313140.9925@racer> (raw)
In-Reply-To: <486C425D.8090904@thewritingpot.com>
Hi,
On Wed, 2 Jul 2008, Edward Z. Yang wrote:
> Johannes Sixt wrote:
> > What about installing a wrapper script, plinkssh, that does this:
> > [snip]
>
> Well, the patch is shorter :-)
But you have to do it for every SSH backend that you might want to
support.
And you have to recompile.
> 1. It's been tested, it works. I haven't tried the script yet, so I
> don't know if it works.
Sorry, that argument does not fly. "My patch is better, because I did not
test your patch."
> 2. Git historically doesn't use bash, so the script would have to be
> rewritten in Perl or plain sh or tcl or something.
That is so totally untrue. We have Perl scripts and Shell scripts (for
which we need the bash), and then we have the two GUIs which use Tcl/Tk.
Actually, we only have so few Perl scripts left that it might be possible
to ship a version of Git on Windows without Perl. The only script that
needs to be converted to a builtin is add -i.
The rest of the scripts are shell.
So this argument is totally bogus.
> 3. It's less brittle than the wrapper script if we decide to have Git
> pass more params to OpenSSH.
Granted, should we decide one day to use more elaborate features of
OpenSSH, then we would have to change the script, too.
But most likely, Plink support would be broken by that update _anyway_,
since it does not grok the OpenSSH options directly.
And guess what is easier to fix, a script that rewrites the arguments from
OpenSSH syntax to Plink syntax, or a C program with over 78,000 code
lines that has to be recompiled?
> 4. It's "more native".
Would it not be even more native if we just linked in libssl? Would you
write the patch?
Further, would you like to convert and maintain all people's wrapper
scripts to C code inside Git?
BTW what is the reason why Hannes' mail does not appear to be the mail
you replied to in GMane, but the patch Steffen sent?
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-03 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 3:07 [PATCH 06/12] connect: Fix custom ports with plink (Putty's ssh) Edward Z. Yang
2008-07-03 12:29 ` Johannes Schindelin [this message]
2008-07-04 20:05 ` Edward Z. Yang
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 8:31 How to reduce remaining differences to 4msysgit? (was What's cooking in git.git (topics)) Steffen Prohaska
2008-07-02 8:32 ` [PATCH 01/12] Fake reencoding success under NO_ICONV instead of returning NULL Steffen Prohaska
2008-07-02 8:32 ` [PATCH 02/12] Do not complain about "no common commits" in an empty repo Steffen Prohaska
2008-07-02 8:32 ` [PATCH 03/12] MinGW: Convert CR/LF to LF in tag signatures Steffen Prohaska
2008-07-02 8:32 ` [PATCH 04/12] Avoid calling signal(SIGPIPE, ..) for MinGW builds Steffen Prohaska
2008-07-02 8:32 ` [PATCH 05/12] Windows(msysgit): Per default, display help as HTML in default browser Steffen Prohaska
2008-07-02 8:32 ` [PATCH 06/12] connect: Fix custom ports with plink (Putty's ssh) Steffen Prohaska
2008-07-02 19:04 ` Johannes Sixt
2008-07-03 11:10 ` Johannes Schindelin
2008-07-04 8:50 ` Steffen Prohaska
2008-07-04 9:18 ` Junio C Hamano
2008-07-04 9:29 ` Steffen Prohaska
2008-07-04 16:09 ` Clifford Caoile
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.00.0807031313140.9925@racer \
--to=johannes.schindelin@gmx.de \
--cc=edwardzyang@thewritingpot.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=junio@pobox.com \
--cc=msysgit@googlegroups.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).