From: Boruch Baum <boruch_baum@gmx.com>
To: 43741@debbugs.gnu.org
Subject: bug#43741: bug acknowledgements use non-TLS http urls
Date: Thu, 1 Oct 2020 08:27:30 -0400 [thread overview]
Message-ID: <20201001122730.znmtsztizok66acj@E15-2016.optimum.net> (raw)
When I receive an automated acknowledgement of a submitted bug report,
the footer of the acknowledgement includes a link to the buf report
thread; for example:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43709
The link should use the https, which from my testing is already
supported by the server.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next reply other threads:[~2020-10-01 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 12:27 Boruch Baum [this message]
2020-10-01 13:03 ` bug#43741: bug acknowledgements use non-TLS http urls Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201001122730.znmtsztizok66acj@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=43741@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).