From: Jason Molenda <jason-gcclist@molenda.com>
To: overseers@gcc.gnu.org
Subject: Re: A problem with the gcc-patches web archives -- please read
Date: Sat, 21 Feb 2004 16:01:00 -0000 [thread overview]
Message-ID: <20040221080103.A59427@molenda.com> (raw)
In-Reply-To: <20040221075735.A57523@molenda.com>; from jason-gcclist@molenda.com on Sat, Feb 21, 2004 at 07:57:35AM -0800
The old directory is saved aside as "2004-02.o".
I'm not sure if the regen will finish before I have to leave
for the day -- it's only about 10% done and I'm out of here
in 25 minutes, no flexibility. The script I'm using to
do this is in the sourceware CVS repo,
infra/ml-archiving/ml-regen-from-txtfiles.sh. With luck it'll
finish without any problems and no one will need to do anything.
But if it doesn't work out, that's what I did.
J
On Sat, Feb 21, 2004 at 07:57:35AM -0800, Jason Molenda wrote:
> The web archiver got stuck for about six hours yesterday.
> It was restarted, but the messages for the six hours it was
> stuck were not archived. The archiving was restarted about
> 24 hours ago.
>
> I'm currently re-generating the web archives for this month.
> It will include the missing 6 hours, but it's important
> to note that the URLs used for those messages will overlap
> with messages archived over the last 24 hours. In short,
> the gcc-patches URLs from the last 24 hours must now be
> considered to be different.
>
> I apologize for that, but there aren't many better ways
> to handle this.
>
> Jason
next prev parent reply other threads:[~2004-02-21 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 15:57 Jason Molenda
2004-02-21 16:01 ` Jason Molenda [this message]
2004-02-21 20:18 ` Jason Molenda
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=20040221080103.A59427@molenda.com \
--to=jason-gcclist@molenda.com \
--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).