From: Junio C Hamano <gitster@pobox.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Ben Goldberg <ben@benaaron.dev>, git@vger.kernel.org
Subject: Re: send-email issue
Date: Sat, 14 Aug 2021 16:36:43 -0700 [thread overview]
Message-ID: <xmqq35rbtx84.fsf@gitster.g> (raw)
In-Reply-To: <20210813180056.ctzivmakj4bj5apa@nitro.local> (Konstantin Ryabitsev's message of "Fri, 13 Aug 2021 14:00:56 -0400")
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> I know that this is confusing terminology, but "tls" stands for "StartTLS",
> which works on port 587, and "ssl" starts for "smtps" on port 465.
This reminds me of an earlier discussion we had that somehow petered
out before it resuted in usable improvement,
https://lore.kernel.org/git/xmqqtuo9kgo0.fsf@gitster.g/
I do not think it is feasible to immediately rename the two choices
to SSL/TLS vs StartTLS without transition period, but the first
patch in the three-patch series there to update the documentation
alone may have helped this case.
We may also want to error out when seeing an unknown option other
than 'ssl' and 'tls', as the necessary first step to make it
possible to later safely accept StartTLS as a synonym for 'tls' and
'ssl/tls' as a synonym for 'ssl'.
next prev parent reply other threads:[~2021-08-14 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 17:50 send-email issue Ben Goldberg
2021-08-13 17:57 ` Ben Goldberg
2021-08-13 18:00 ` Ben Goldberg
2021-08-13 18:00 ` Konstantin Ryabitsev
2021-08-13 18:03 ` Ben Goldberg
2021-08-14 23:36 ` Junio C Hamano [this message]
2021-08-16 13:11 ` Konstantin Ryabitsev
2021-08-16 16:19 ` Jeff King
2021-08-16 16:51 ` Junio C Hamano
2021-08-16 16:57 ` Jeff King
2021-08-16 18:52 ` Junio C Hamano
2021-08-23 14:49 ` Ævar Arnfjörð Bjarmason
2021-08-24 21:45 ` Junio C Hamano
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=xmqq35rbtx84.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben@benaaron.dev \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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 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).