public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: overseers@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: web/3119: Broken gcc mailing list archives
Date: Fri, 13 Dec 2002 11:26:00 -0000 [thread overview]
Message-ID: <20021213192605.13254.qmail@sources.redhat.com> (raw)
The following reply was made to PR web/3119; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: web/3119: Broken gcc mailing list archives
Date: Fri, 13 Dec 2002 19:23:26 +0000 (GMT)
On Fri, 13 Dec 2002, Volker Reichelt wrote:
> IMHO the problems got fixed.
> Could you please check and close the PR?
I fixed the bulk of the problems by restoring the damaged or lost files
from directories before the month of the damage from backup (actually, the
old sourcewre disk). I have not made detailed manual checks of the months
/ quarters / years (depending on what goes in one directory) of the damage
for problems (since files in those directories naturally changed for
updates of threads etc.) - the appropriate action for those directories is
probably to generate -n versions of the directories (as done previously in
some cases where regeneration was wanted) from the mbox files (or from the
qmail archives, in the case of gcc-cvs-wwwdocs which doesn't / didn't have
FTP mbox archives).
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2002-12-13 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 11:26 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 7:06 Volker Reichelt
2001-06-12 9:17 jsm28
2001-06-12 5:17 gerald
2001-06-11 2:26 Joseph Myers
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=20021213192605.13254.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=overseers@gcc.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.
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).