From: Jason Molenda <jason@molenda.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sources.redhat.com
Subject: Re: http://gcc.gnu.org/ml/gcc-prs/
Date: Fri, 21 Jul 2000 13:21:00 -0000 [thread overview]
Message-ID: <20000721132027.A13293@shell17.ba.best.com> (raw)
Message-ID: <20000721132100.JPAt5-VuRk_CVh267MLPgsUrVfraVu1wP5e4PghWc7A@z> (raw)
In-Reply-To: <Pine.BSF.4.21.0007212115300.4863-100000@deneb.dbai.tuwien.ac.at>
On Fri, Jul 21, 2000 at 09:17:46PM +0200, Gerald Pfeifer wrote:
> Okay, so I also fixed it manually for gcc-prs, though I'm afraid there
> might be a bug in some script that will bite again.
None of the quarterly lists were updated correctly on July 1 - I had a
small bug in the updater script. I fixed the bug and updated all of them
by hand (or so I thought :-).
Shouldn't happen again.
J
next prev parent reply other threads:[~2000-07-21 13:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.21.0007141909160.85825-100000@taygeta.dbai.tuwien.ac.at>
2000-12-30 6:08 ` gcc-prs -> gcc-bugs Gerald Pfeifer
2000-07-20 10:17 ` Gerald Pfeifer
2000-12-30 6:08 ` Tom Tromey
2000-07-20 14:45 ` Tom Tromey
2000-12-30 6:08 ` Gerald Pfeifer
2000-08-04 17:00 ` Gerald Pfeifer
2000-12-30 6:08 ` Gerald Pfeifer
2000-08-10 6:50 ` Gerald Pfeifer
2000-12-30 6:08 ` Jeffrey A Law
2000-08-10 9:55 ` Jeffrey A Law
2000-12-30 6:08 ` http://gcc.gnu.org/ml/gcc-prs/ Gerald Pfeifer
2000-07-21 2:35 ` http://gcc.gnu.org/ml/gcc-prs/ Gerald Pfeifer
2000-12-30 6:08 ` http://gcc.gnu.org/ml/gcc-prs/ Jim Kingdon
2000-07-21 8:24 ` http://gcc.gnu.org/ml/gcc-prs/ Jim Kingdon
2000-12-30 6:08 ` http://gcc.gnu.org/ml/gcc-prs/ Gerald Pfeifer
2000-07-21 12:49 ` http://gcc.gnu.org/ml/gcc-prs/ Gerald Pfeifer
2000-12-30 6:08 ` Jason Molenda [this message]
2000-07-21 13:21 ` http://gcc.gnu.org/ml/gcc-prs/ Jason Molenda
2000-12-30 6:08 ` http://gcc.gnu.org/ml/gcc-prs/ Chris Faylor
2000-07-21 12:52 ` http://gcc.gnu.org/ml/gcc-prs/ Chris Faylor
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=20000721132027.A13293@shell17.ba.best.com \
--to=jason@molenda.com \
--cc=overseers@sources.redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).