git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Ben Goldberg <ben@benaaron.dev>,
	git@vger.kernel.org
Subject: Re: send-email issue
Date: Mon, 16 Aug 2021 11:52:42 -0700	[thread overview]
Message-ID: <xmqqzgthql1h.fsf@gitster.g> (raw)
In-Reply-To: <YRqY4Tw4YxbepuFg@coredump.intra.peff.net> (Jeff King's message of "Mon, 16 Aug 2021 12:57:05 -0400")

Jeff King <peff@peff.net> writes:

> This is certainly unfortunate, but IMHO is not a hard requirement for
> adding new values. This is no different than a case where we add a new
> config option, but old versions of Git quietly ignore it.
>
> In other words, I would suggest to tighten this as the values are added,
> but not worry about having a "spreading" period.

I would have agreed with you even in April if this knob were not
about security.  Thinking that the user is asking for an encrypted
connection and silently getting an unencrypted connection is not
such a good thing, and advertising "we now improved the distinction
between smtps and starttls easier to express" to users would not
work well in that context.


  reply	other threads:[~2021-08-16 18:52 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
2021-08-16 16:51           ` Junio C Hamano
2021-08-16 16:57             ` Jeff King
2021-08-16 18:52               ` Junio C Hamano [this message]
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=xmqqzgthql1h.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben@benaaron.dev \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=peff@peff.net \
    /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).