All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Ben Goldberg <ben@benaaron.dev>,
	git@vger.kernel.org
Subject: Re: send-email issue
Date: Mon, 16 Aug 2021 12:19:49 -0400	[thread overview]
Message-ID: <YRqQJTyBW6j6b2pW@coredump.intra.peff.net> (raw)
In-Reply-To: <20210816131143.6ifcbpxp6ilo2nv5@nitro.local>

On Mon, Aug 16, 2021 at 09:11:43AM -0400, Konstantin Ryabitsev wrote:

> > 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'.
> 
> Is it easier to just add less ambiguous aliases, eventually phasing out old
> terminology?
> 
> tls -> starttls
> ssl -> smtps
> 
> This way we don't have to change anything, and "smtps" is a valid way to refer
> to smtp over ssl (e.g. see /etc/services for 465/tcp).

FWIW, those options make quite a bit of sense to me (and I agree the
transition to them would be easy).

-Peff

  reply	other threads:[~2021-08-16 16:19 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
2021-08-16 13:11       ` Konstantin Ryabitsev
2021-08-16 16:19         ` Jeff King [this message]
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=YRqQJTyBW6j6b2pW@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=ben@benaaron.dev \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.