From: Daniel Berlin <dberlin@dberlin.org>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.3 Branch Open
Date: Thu, 15 May 2003 00:12:00 -0000 [thread overview]
Message-ID: <E393D06B-8669-11D7-A533-000A95A34564@dberlin.org> (raw)
In-Reply-To: <1052956124.1498.60.camel@doubledemon.codesourcery.com>
On Wednesday, May 14, 2003, at 07:48 PM, Mark Mitchell wrote:
> The GCC 3.3 branch is now open for regression-fixes only, under the
> usual release branch rules.
>
> Also, how do I find bugzilla? The release checklist has some bugzilla
> activity for me, but I'm not sure what URL to use. (The best thing
> would be if someone would insert a link in the release notes;
> otherwise,
> please send me the URL and I will take care of it.)
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.
:)
>
> On that note, we may as well switch from GNATS to bugzilla now, if
> bugzilla is ready to go.
It is, actually, but it requires a bit of coordination among people.
So i'll send out a seperate message about it.
>
> Thanks!
>
> --
> Mark Mitchell
> CodeSourcery, LLC
> mark@codesourcery.com
>
next prev parent reply other threads:[~2003-05-15 0:12 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 [this message]
2003-05-15 10:19 ` Joseph S. Myers
2003-05-15 14:04 ` Daniel Berlin
2003-05-15 15:59 ` Daniel Berlin
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=E393D06B-8669-11D7-A533-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--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).