From: Junio C Hamano <firstname.lastname@example.org>
To: Sven Strickroth <email@example.com>
Cc: git <firstname.lastname@example.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: tortoiseplink ssh variant still needed?
Date: Sat, 23 Oct 2021 14:53:33 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Sven Strickroth's message of "Fri, 22 Oct 2021 18:13:20 +0200")
Sven Strickroth <email@example.com> writes:
> IIRC tortoiseplink was initially created by TortoiseCVS which is
> nowadays not maintained any more
> In TortoiseSVN and TortoiseGit tortoiseplink was modified six years
> ago (around 2015-03-07) to ignore the "--batch" parameter and also
> accept "-p" additionally to "-P" (cf.
> Therefore, my first question: Does Git still want to support very old
> versions of tortoiseplink or should I provide a patch which drops
> support for it?
You sent the question to me so I am answering, but this depends on
(1) who the users who use TortoisePlink are and (2) by dropping
support for it, what we would gain.
I am guessing that nobody other than those on Windows use
TortoisePlink, and that everybody other than those who build their
own Git from source use Dscho's Git-for-Windows, and I further
assume that the GfW comes with its own copy of OpenSSH.
So our intended audience is those who started using Git on Windows
back when TortoisePlink was still a thing, are still happily using
TortoisePlink, and are willing to only update Git but not migrate to
OpenSSH. How big that audience is, I do not know, as I do not do
How much maintenance burden is the "support" costing us? A quick
scan in connect.c tells me that the "add --batch to the command
line" would be the only thing we would be able to shed; everything
else seems to be shared with plink and putty.
next prev parent reply other threads:[~2021-10-23 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 16:13 tortoiseplink ssh variant still needed? Sven Strickroth
2021-10-22 16:45 ` [PATCH] Drop unneeded special handling of ssh variant tortoiseplink Sven Strickroth
2021-10-23 9:57 ` Ævar Arnfjörð Bjarmason
2021-10-23 21:53 ` Junio C Hamano [this message]
2021-10-25 13:04 ` tortoiseplink ssh variant still needed? Johannes Schindelin
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:
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 \
* 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
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).