From: Daniel Berlin <dberlin@dberlin.org>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>,
"Joseph S. Myers" <jsm28@cam.ac.uk>
Subject: Re: GCC 3.3 Branch Open
Date: Thu, 15 May 2003 15:59:00 -0000 [thread overview]
Message-ID: <2AC97E92-86EE-11D7-81C9-000A95A34564@dberlin.org> (raw)
In-Reply-To: <F40B690F-86DD-11D7-81C9-000A95A34564@dberlin.org>
On Thursday, May 15, 2003, at 10:03 AM, Daniel Berlin wrote:
>
> On Thursday, May 15, 2003, at 06:18 AM, Joseph S. Myers wrote:
>
>> On Wed, 14 May 2003, Daniel Berlin wrote:
>>
>>> http://gcc.gnu.org/bugzilla
>>>
>>> There is nothing for you to do yet in Bugzilla, since any changes you
>>> made to the DB would be wiped out during final conversion anyway.
>>> :)
>>
>> What's with the various different converter scripts (bug_email.pl,
>> gnatsparse.py),
>
> gnatsparse is for converting gnats to bugzilla.
> bug_email.pl is an inbound email handler that converts gccbug reports
> to bugzilla ones.
> I've already updated both for 3.3.1.
actually, Mark beat me to updating bug_email.pl
:)
----------------------------
revision 1.7
date: 2003/05/14 23:38:33; author: mmitchel; state: Exp; lines: +4 -1
Update for 3.3.1
next prev parent reply other threads:[~2003-05-15 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 23:48 Mark Mitchell
2003-05-15 0:12 ` Daniel Berlin
2003-05-15 10:19 ` Joseph S. Myers
2003-05-15 14:04 ` Daniel Berlin
2003-05-15 15:59 ` Daniel Berlin [this message]
2003-05-15 12:41 ` Gerald Pfeifer
2003-05-15 14:08 ` Daniel Berlin
2003-08-08 19:03 GCC 3.3 branch open Mark Mitchell
2003-08-08 20:05 ` Kelley Cook
2003-08-08 20:16 ` Mark Mitchell
2003-10-17 19:30 GCC 3.3 Branch Open Mark Mitchell
2003-10-18 15:53 ` Eric Botcazou
2003-10-20 6:12 ` Mark Mitchell
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=2AC97E92-86EE-11D7-81C9-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
--cc=mark@codesourcery.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).