public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Phil Edwards <phil@jaj.com>, Michael Elizabeth Chastain <mec@shout.net>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: What are the chances of another release from gcc-3_2-branch?
Date: Thu, 19 Dec 2002 11:31:00 -0000	[thread overview]
Message-ID: <60950000.1040324560@warlock.codesourcery.com> (raw)
In-Reply-To: <20021219005413.A31681@disaster.jaj.com>



--On Thursday, December 19, 2002 12:54:13 AM -0500 Phil Edwards 
<phil@jaj.com> wrote:

> On Sun, Dec 15, 2002 at 10:42:01PM -0600, Michael Elizabeth Chastain
> wrote:
>> My question: is it safe for me to stop testing gcc-3_2-branch?  That is,
>> what are the chances of another gcc release such as a "gcc 3.2.2" coming
>> from the gcc-3_2-branch?

I don't think any decision has been made.  Personally, I'm trying to focus
on 3.3/3.4; there's plenty enough to do there.  But, if people want another
3.2 release we can do one.

If someone else wants to step forward to run a 3.2.2 release, that would
be fine, too.

Thanks,

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

  reply	other threads:[~2002-12-19 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 21:46 Michael Elizabeth Chastain
2002-12-19  0:15 ` Phil Edwards
2002-12-19 11:31   ` Mark Mitchell [this message]
2002-12-19 13:19     ` Joe Buck
2002-12-19 15:16       ` Eric Botcazou
2002-12-27 13:21     ` Gabriel Dos Reis
2002-12-27 12:46 ` Gerald Pfeifer
2002-12-19 13:15 Kaveh R. Ghazi
2002-12-19 15:25 ` Tom Tromey
2002-12-19 22:13   ` Kaveh R. Ghazi
2002-12-19 15:23 Michael Elizabeth Chastain
2002-12-20  9:02 Volker Reichelt
2002-12-27 23:58 Michael Elizabeth Chastain
2002-12-28  3:47 John David Anglin

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=60950000.1040324560@warlock.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mec@shout.net \
    --cc=phil@jaj.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).