public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/20588] New: gcc-patches 2004-02 archives broken
Date: Tue, 22 Mar 2005 18:58:00 -0000	[thread overview]
Message-ID: <20050322125533.20588.jsm28@gcc.gnu.org> (raw)

Most of the messages in the gcc-patches archives for 2004-02 are missing (links
from the index are broken).

Some messages on the subject from overseers at the time, which are missing from
the online overseers archive (perhaps all the archives from around that time
need regenerating; grep suggests the problem log message appears for other
months as well which may need the same treatment): 6594-6604 (ezmlm message
numbers).  Extracts:

6595: "Don't know what's causing it but this is the reason:

gcc-patches/Log:ERROR: Unable to lock /www/gcc/ml/gcc-patches/2004-02 after 10
tries"

6596: "Luckily the plain text files are still being created in txt/.  The
mhonarc archvies can be removed and regen'ed from that easily.  That
will keep them in the same order."

6597: "e.g. with a slight modification to 
/sourceware/infra/ml-archiving/ml-fill-in.sh."

6604: "It looks like my stupid notebook went to sleep while the regen
was still happening -- it did not finish.

I'll restart.  With sleep disabled."

MHonarc can detect duplicates using message-id.  Perhaps all the mbox and
qmail archives should be fed into the archives for past months again to
fill in anything that is missing (whether or not it is known that anything
is missing in each particular case)?

-- 
           Summary: gcc-patches 2004-02 archives broken
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: web
        AssignedTo: overseers at gcc dot gnu dot org
        ReportedBy: jsm28 at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20588

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2005-03-22 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 18:58 jsm28 at gcc dot gnu dot org [this message]
2005-03-22 19:14 ` [Bug web/20588] " jsm28 at gcc dot gnu dot org
2005-08-17 23:18 ` pinskia at gcc dot gnu dot org

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=20050322125533.20588.jsm28@gcc.gnu.org \
    --to=gcc-bugzilla@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).