This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Version numbers
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Version numbers
- From: Jeffrey A Law <law at redhat dot com>
- Date: Fri, 16 Feb 2001 09:27:41 -0700
- cc: Mark Mitchell <mark at codesourcery dot com>, "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, gcc at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <Pine.BSF.4.33.0102160912480.55228-100000@deneb.dbai.tuwien.ac.at>
you write:
> On Fri, 16 Feb 2001, Mark Mitchell wrote:
> >> Will do, for the script that updates the branch.
> > Thanks. See subsequent mail about the account set up to do this in.
>
> In three minutes we'll know whether it works:
>
> [gccadmin ~/scripts]$ crontab -l
> 16 0 * * * sh /home/gccadmin/scripts/update_version
>
> Ha, it worked! :-)
Ugh. Calling it "update_version" wasn't all that smart. Now we have two
"update_version" scripts. One in the gccadmin tree, one in mine. They
do two different things. One updates the mainline version (my tree), the
other updates the branch (gccadmin tree).
I've fixed this by moving both my scripts (update_version and
update_branch_version) into the gccadmin tree and updating the various
cron jobs appropriately.
One could probably collapse them into a single script and have cron pass
the script an argument indicating what branch to change the version
strings on. I leave that as an exercise to interested readers as I
don't have the time right now...
jeff