From: Mark Mitchell <mark@codesourcery.com>
To: Zack Weinberg <zack@codesourcery.com>,
Nathanael Nerode <neroden@doctormoo.dyndns.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: "Have we branched yet?"
Date: Wed, 16 Oct 2002 12:53:00 -0000 [thread overview]
Message-ID: <319430000.1034792184@warlock.codesourcery.com> (raw)
In-Reply-To: <20021016041339.GV15067@codesourcery.com>
--On Tuesday, October 15, 2002 09:13:39 PM -0700 Zack Weinberg
<zack@codesourcery.com> wrote:
> On Wed, Oct 16, 2002 at 12:04:14AM -0400, Nathanael Nerode wrote:
>> Have we branched yet?
>
> It's Mark's call, but I don't think the tree is in shape to be
> branched. Wanna fix some bugs?
Exactly right. My first priority is GCC 3.2.1, which needs high-priority
bugs to go away first. Branching GCC 3.3 is a secondary priority, and
that needs high-priority bugs to go away too.
There's been some bug-fixing activity, but we need lots more!
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
prev parent reply other threads:[~2002-10-16 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 1:53 Nathanael Nerode
2002-10-16 2:07 ` Zack Weinberg
2002-10-16 12:53 ` Mark Mitchell [this message]
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=319430000.1034792184@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@doctormoo.dyndns.org \
--cc=zack@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).