From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: rm -rf /www/gcc/htdocs/usage/
Date: Thu, 10 Nov 2022 11:08:27 +0100 [thread overview]
Message-ID: <f8ee449fa76a0180053d8f88fdf01495f24dd7aa.camel@klomp.org> (raw)
In-Reply-To: <c5113b37-58b6-acf5-8f75-265ada1fa999@pfeifer.com>
Hi Gerald,
On Wed, 2022-11-09 at 23:07 +0100, Gerald Pfeifer via Overseers wrote:
> would you mind removing /www/gcc/htdocs/usage/ which looks like a
> remainder of an experiment someone seems to have done in 2013.
It is gone.
Archived just in case as /sourceware/archive/www-gcc-htdocs-
usage.tar.gz but it can probably just be erased because it doesn't
really look useful.
Cheers,
Mark
prev parent reply other threads:[~2022-11-10 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 22:07 Gerald Pfeifer
2022-11-10 10:08 ` Mark Wielaard [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=f8ee449fa76a0180053d8f88fdf01495f24dd7aa.camel@klomp.org \
--to=mark@klomp.org \
--cc=gerald@pfeifer.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).