From: "Edward Z. Yang" <edwardzyang@thewritingpot.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: msysGit <msysgit@googlegroups.com>,
git@vger.kernel.org, gitster@pobox.com, junio@pobox.com
Subject: Re: [PATCH 06/12] connect: Fix custom ports with plink (Putty's ssh)
Date: Fri, 04 Jul 2008 16:05:48 -0400 [thread overview]
Message-ID: <486E829C.608@thewritingpot.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807031313140.9925@racer>
> Sorry, that argument does not fly. "My patch is better, because I did not
> test your patch."
Just tested, the patch works.
> 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.
I came up with that conclusion by grepping the Git source code for the
word bash; no results. Granted, it's still a null point because the
proposed script doesn't use any bash-specific features.
> Further, would you like to convert and maintain all people's wrapper
> scripts to C code inside Git?
I was under the impression that wrapper scripts were for fleshing out
new APIs and implementing non-performance critical functionality,
without all the overhead of writing in C. There is little to no overhead
from this patch.
Anyway, Johannes still makes some pretty compelling points for the
wrapper script, so you can count me +1 for the wrapper.
> 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?
I actually did a "Reply" and so he was the only one who got the email at
first. Then I resent it to the list, as well as the other CC'ed people.
(Thus my comment at the bottom)
next prev parent reply other threads:[~2008-07-04 20:07 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
2008-07-04 20:05 ` Edward Z. Yang [this message]
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486E829C.608@thewritingpot.com \
--to=edwardzyang@thewritingpot.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).