Re: Automatically update version_string for autovect-branch

[Sebastian Pop <sebastian dot pop at cri dot ensmp dot fr>]

Gerald Pfeifer wrote:
> On Thu, 30 Dec 2004, Sebastian Pop wrote:
> > The following patches make the version_string of autovect-branch to be
> > automatically updated.  Are these two patches okay?
> > 
> > 	* update_version (ADD_BRANCHES): Replace lno-branch with 
> > 	autovect-branch.
> 
> Yes.  Please apply this to mainline and I'll take care of the gcc.gnu.org
> side of things.
> 

Applied to mainline.

> > in autovect-branch:
> > 
> > 	* version.c (version_string): Automatically update the name of 
> > 	the branch.
> 
> > -const char version_string[] = "4.0.0 20041213 (experimental)";
> > +const char version_string[] = "4.0.0-autovect 20041230 (autovect-merge-20041213)";
> 
> Don't we usually keep the "experimental"?  I think that would be nice to 
> have, perhaps "(experimental, autovect-merge...)"?
> 

I have committed the following in autovect-branch.

*** version.c.~1.2512.2.1.~	Sun Dec 19 02:35:34 2004
--- version.c	Fri Dec 31 01:07:19 2004
***************
*** 5,11 ****
     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[] = "4.0.0 20041213 (experimental)";
  
  /* This is the location of the online document giving instructions for
     reporting bugs.  If you distribute a modified version of GCC,
--- 5,11 ----
     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[] = "4.0.0-autovect 20041230 (experimental, autovect-merge-20041213)";
  
  /* This is the location of the online document giving instructions for
     reporting bugs.  If you distribute a modified version of GCC,