From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "Andrew Haley" <aph@redhat.com>,
"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Paolo Bonzini" <bonzini@gnu.org>,
gcc@gcc.gnu.org
Subject: Re: archives broken?
Date: Wed, 06 May 2009 22:25:00 -0000 [thread overview]
Message-ID: <4A020C81.1010802@gmail.com> (raw)
In-Reply-To: <m3eiv2c9wb.fsf@google.com>
Ian Lance Taylor wrote:
> Andrew Haley <aph@redhat.com> writes:
>
>> Manuel López-Ibáñez wrote:
>>> 2009/5/6 Paolo Bonzini <bonzini@gnu.org>:
>>>> It looks like a bunch of missing from
>>>> http://gcc.gnu.org/ml/gcc-patches/2004-02/ are missing. Anybody knows
>>>> what could be the cause?
>>> Relevant PRs 20336, 20588, 3119.
>> I'm pretty sure I have a complete set of the messages.
>
> I believe that we have a complete set of messages too. Fixing the web
> pages takes somebody with the time and energy to figure out what is
> required. The mailing list archives are built using mhonarc. Any
> volunteers?
I could have a rummage. I have a little experience with mhonarc, having
installed and maintained some in-house mailing list archives in my last job.
I never had to rebuild an index, but I recall reading that it's fairly
straightforward to feed it emails in mbox format and get it to rebuild the
indices (which hopefully should all line-up as they were before rather than
result in any message numbers shifting about).
cheers,
DaveK
next prev parent reply other threads:[~2009-05-06 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 17:22 Paolo Bonzini
2009-05-06 17:28 ` Dave Korn
2009-05-06 17:34 ` Manuel López-Ibáñez
2009-05-06 17:35 ` Andrew Haley
2009-05-06 19:25 ` Joseph S. Myers
2009-05-06 19:57 ` Ian Lance Taylor
2009-05-06 22:25 ` Dave Korn [this message]
2009-05-06 22:34 ` Joseph S. Myers
2009-05-06 22:43 ` Dave Korn
2009-05-06 22:53 ` Joseph S. Myers
2009-05-06 23:07 ` Dave Korn
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=4A020C81.1010802@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=aph@redhat.com \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=lopezibanez@gmail.com \
/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).