public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: gcc@gcc.gnu.org
Subject: gcc-2.95.2 rough plan
Date: Tue, 07 Sep 1999 01:10:00 -0000	[thread overview]
Message-ID: <23106.936691715@upchuck.cygnus.com> (raw)

Just to let folks know what the rough plan is for gcc-2.95.2.

I would like to have gcc-2.95.2 hit the streets somewhere between Oct 1 and
Oct 15.  The plan (like all our minor releases) is to just fix serious bugs
that have simple and safe bugfixes.

It is very important that the proposed fixes be kept simple.  Testing before
a minor release is limited; therefore, we only want to install fixes that we
know to be very safe.

Maintainers are free to check in changes to the gcc-2.95 branch in areas of
the compiler they maintain within the guidelines noted above.

I do ask that anyone checking in changes to the gcc-2.95 branch send me 
a very short (1-2 line) description of the problem that is solved by the
change (for the release notes).

Comments and suggestions are always encouraged!


Thanks,

jeff

WARNING: multiple messages have this Message-ID

From: Jeffrey A Law <law@cygnus.com>
To: gcc@gcc.gnu.org
Subject: gcc-2.95.2 rough plan
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <23106.936691715@upchuck.cygnus.com> (raw)
Message-ID: <19990930180200.tdScFMl3euLLzDRBklIlnc5FKLrgMUd-kJDsP2JQ1lU@z> (raw)

Just to let folks know what the rough plan is for gcc-2.95.2.

I would like to have gcc-2.95.2 hit the streets somewhere between Oct 1 and
Oct 15.  The plan (like all our minor releases) is to just fix serious bugs
that have simple and safe bugfixes.

It is very important that the proposed fixes be kept simple.  Testing before
a minor release is limited; therefore, we only want to install fixes that we
know to be very safe.

Maintainers are free to check in changes to the gcc-2.95 branch in areas of
the compiler they maintain within the guidelines noted above.

I do ask that anyone checking in changes to the gcc-2.95 branch send me 
a very short (1-2 line) description of the problem that is solved by the
change (for the release notes).

Comments and suggestions are always encouraged!


Thanks,

jeff

             reply	other threads:[~1999-09-07  1:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-07  1:10 Jeffrey A Law [this message]
1999-09-07  3:33 ` John Vickers
1999-09-07  4:21   ` Jeffrey A Law
1999-09-30 18:02     ` Jeffrey A Law
1999-09-30 18:02   ` John Vickers
1999-09-07 14:53 ` craig
1999-09-07 15:09   ` Jeffrey A Law
1999-09-07 16:24     ` craig
1999-09-07 17:30       ` Richard Henderson
1999-09-30 18:02         ` Richard Henderson
1999-09-30 18:02       ` craig
1999-09-30 18:02     ` Jeffrey A Law
1999-09-30 18:02   ` craig
1999-09-08  9:02 ` Joel Klecker
1999-09-30 18:02   ` Joel Klecker
1999-09-30 18:02 ` Jeffrey A Law
1999-09-08 16:23 Billinghurst, David (RTD)
1999-09-08 16:59 ` Jeffrey A Law
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Billinghurst, David (RTD)

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=23106.936691715@upchuck.cygnus.com \
    --to=law@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    /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).