From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <firstname.lastname@example.org>
Cc: Sven Strickroth <email@example.com>, git <firstname.lastname@example.org>
Subject: Re: tortoiseplink ssh variant still needed?
Date: Mon, 25 Oct 2021 15:04:35 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.email@example.com> (raw)
On Sat, 23 Oct 2021, Junio C Hamano wrote:
> Sven Strickroth <firstname.lastname@example.org> writes:
> > 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?
> 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
Nobody really knows, but we started discouraging `plink` usage (also
`tortoiseplink` usage) already way back in the msysGit days. AFAIR we
simply ran into too much trouble, and started to only offer `plink` as an
option if the user had _any_ PuTTY saved sessions.
> 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.
Since I have to assume a very small usership, I would think that we can
drop support for the older `tortoiseplink`. But you're right, what does it
My guess is that Sven wants to go further and enable the `-o SetEnv` thing
for protocol v2 (which we figured out together, over in the Git for
Windows bug tracker, to be turned off when pushing). But that would
require the `tortoisegitplink` variant, I think.
So maybe a better idea would be to focus on introducing support for
`tortoisegitplink` and work on the `-o SetEnv` issue, and leave the
`--batch` code alone for now.
prev parent reply other threads:[~2021-10-25 13:04 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 ` tortoiseplink ssh variant still needed? Junio C Hamano
2021-10-25 13:04 ` Johannes Schindelin [this message]
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).