public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: GCC 3.3 Branch Open
Date: Mon, 20 Oct 2003 06:12:00 -0000	[thread overview]
Message-ID: <1066605997.3314.38.camel@minax.codesourcery.com> (raw)
In-Reply-To: <200310181431.26593.ebotcazou@libertysurf.fr>

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

On Sat, 2003-10-18 at 05:31, Eric Botcazou wrote:
> > The GCC 3.3 branch is now open for regression-only changes again.
> 
> Don't you need to bump the version number on the branch?

Yes, thank you.

-- 
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2810 bytes --]

2003-10-19  Mark Mitchell  <mark@codesourcery.com>

	* doc/include/gcc-common.texi: Bump version number.
	* version.c (version_string): Reset to prerelease format.

Index: version.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/version.c,v
retrieving revision 1.1810.2.315
diff -c -5 -p -r1.1810.2.315 version.c
*** version.c	16 Oct 2003 19:45:43 -0000	1.1810.2.315
--- version.c	19 Oct 2003 23:15:30 -0000
***************
*** 4,14 ****
  /* This is the string reported as the version number by all components
     of the compiler.  If you distribute a modified version of GCC,
     please modify this string to indicate that, e.g. by putting your
     organization's name in parentheses at the end of the string.  */
  
! const char version_string[] = "3.3.2";
  
  /* This is the location of the online document giving instructions for
     reporting bugs.  If you distribute a modified version of GCC,
     please change this to refer to a document giving instructions for
     reporting bugs to you, not us.  (You are of course welcome to
--- 4,14 ----
  /* This is the string reported as the version number by all components
     of the compiler.  If you distribute a modified version of GCC,
     please modify this string to indicate that, e.g. by putting your
     organization's name in parentheses at the end of the string.  */
  
! const char version_string[] = "3.3.3 20031019 (prerelease)";
  
  /* This is the location of the online document giving instructions for
     reporting bugs.  If you distribute a modified version of GCC,
     please change this to refer to a document giving instructions for
     reporting bugs to you, not us.  (You are of course welcome to
Index: doc/include/gcc-common.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/include/gcc-common.texi,v
retrieving revision 1.3.14.3
diff -c -5 -p -r1.3.14.3 gcc-common.texi
*** doc/include/gcc-common.texi	7 Aug 2003 20:12:35 -0000	1.3.14.3
--- doc/include/gcc-common.texi	19 Oct 2003 23:15:30 -0000
***************
*** 2,12 ****
  @c This is part of the GCC manual.
  @c For copying conditions, see the file gcc.texi.
  
  @c Common values used in the GCC manuals:
  
! @set version-GCC 3.3.2
  
  @c DEVELOPMENT is set to indicate an in-development version,
  @c as compared to a release version.  When making a release
  @c branch, clear this.
  @clear DEVELOPMENT
--- 2,12 ----
  @c This is part of the GCC manual.
  @c For copying conditions, see the file gcc.texi.
  
  @c Common values used in the GCC manuals:
  
! @set version-GCC 3.3.3
  
  @c DEVELOPMENT is set to indicate an in-development version,
  @c as compared to a release version.  When making a release
  @c branch, clear this.
  @clear DEVELOPMENT

  reply	other threads:[~2003-10-19 23:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 19:30 Mark Mitchell
2003-10-18 15:53 ` Eric Botcazou
2003-10-20  6:12   ` Mark Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-05-14 23:48 GCC 3.3 Branch Open 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
2003-05-15 12:41   ` Gerald Pfeifer
2003-05-15 14:08     ` Daniel Berlin

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=1066605997.3314.38.camel@minax.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=ebotcazou@libertysurf.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --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).