From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, "Gerald Pfeifer" <gerald@pfeifer.com>,
"Martin Liška" <mliska@suse.cz>
Subject: Re: Minor edition to /etc/httpd/conf.d/sourceware-vhost-gcc.conf
Date: Sat, 12 Nov 2022 11:09:22 +0100 [thread overview]
Message-ID: <Y29w0m0pz1h8VGMp@wildebeest.org> (raw)
In-Reply-To: <575d7f0b-7e87-cd4c-9942-1353d8c82e10@pfeifer.com>
Hi Gerald,
On Sat, Nov 12, 2022 at 10:43:48AM +0100, Gerald Pfeifer via Overseers wrote:
> Can you please extend this to also cover /install ?
Done. https://gcc.gnu.org/install looks good to me now.
Cheers,
Mark
next prev parent reply other threads:[~2022-11-12 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 9:43 Gerald Pfeifer
2022-11-12 10:09 ` Mark Wielaard [this message]
2022-11-14 11:14 ` Florian Weimer
2022-11-14 11:18 ` Gerald Pfeifer
2022-11-14 13:33 ` Martin Liška
2022-11-14 13:55 ` Gerald Pfeifer
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=Y29w0m0pz1h8VGMp@wildebeest.org \
--to=mark@klomp.org \
--cc=gerald@pfeifer.com \
--cc=mliska@suse.cz \
--cc=overseers@gcc.gnu.org \
--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).