From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Jason Merrill <jason@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: gcc.sourceware.org
Date: Fri, 30 Apr 2021 11:54:33 -0400 [thread overview]
Message-ID: <20210430155433.GA4288@cgf.cx> (raw)
In-Reply-To: <CADzB+2maZ9R3FK1M5xvd+WGZXtCMLVQGBPfy94MZm8Jjgf80YA@mail.gmail.com>
On Fri, Apr 30, 2021 at 12:23:02AM -0400, Jason Merrill wrote:
>I'm not sure if anyone from the steering committee has already reached
>out to you about this, but we'd like to be able to access the GCC
>website using a non-gnu.org address in case the DNS for gcc.gnu.org
>becomes an issue.
Sounds like a good idea.
cgf
next prev parent reply other threads:[~2021-04-30 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 4:23 gcc.sourceware.org Jason Merrill
2021-04-30 15:54 ` Christopher Faylor [this message]
2021-04-30 16:42 ` gcc.sourceware.org Joseph Myers
2021-05-01 3:07 ` gcc.sourceware.org Carlos O'Donell
2021-05-01 3:17 ` gcc.sourceware.org Jason Merrill
2021-05-01 4:19 ` gcc.sourceware.org Carlos O'Donell
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=20210430155433.GA4288@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=jason@redhat.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).