From: "Frank Ch. Eigler" <fche@elastic.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: sourceware.org expired certificate
Date: Tue, 14 Apr 2020 17:47:00 -0400 [thread overview]
Message-ID: <20200414214700.GM1661286@elastic.org> (raw)
In-Reply-To: <CAGWvny=a1o0rCtZAA-1500f+XJ8aM8U6hAEiuePr1W_1AgB=4A@mail.gmail.com>
Hi -
> ecos.sourceware.org doesn't seem to allow TLS. I don't know if that
> is what the person was trying to report.
OK, fixed that.
- FChE
prev parent reply other threads:[~2020-04-14 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 21:55 David Edelsohn
2020-04-13 22:37 ` Frank Ch. Eigler
2020-04-14 21:27 ` David Edelsohn
2020-04-14 21:47 ` Frank Ch. Eigler [this message]
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=20200414214700.GM1661286@elastic.org \
--to=fche@elastic.org \
--cc=dje.gcc@gmail.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).