aboutsummaryrefslogtreecommitdiff
path: root/gdb/version.in
AgeCommit message (Collapse)AuthorFilesLines
2019-10-06Change gdb/version.in to 9.0.50.DATE-git (new version numbering scheme)Joel Brobecker1-1/+1
gdb/ChangeLog: * version.in: Change version number to "9.0.50.DATE-git".
2019-02-27Bump version to 8.3.50.DATE-git.Joel Brobecker1-1/+1
Now that the GDB 8.3 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 8.3 branch created (143420fb0d5ae54323ba9953f0818c194635228d): * version.in: Bump version to 8.3.50.DATE-git.
2018-07-04Bump version to 8.2.50.DATE-git.Joel Brobecker1-1/+1
Now that the GDB 8.2 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 8.2 branch created (1b919490e8ba30bf1d6941df0ed112b0e557017e): * version.in: Bump version to 8.2.50.DATE-git.
2018-01-05Bump version to 8.1.50.DATE-git.Joel Brobecker1-1/+1
Now that the GDB 8.1 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 8.1 branch created (5219ac6237c272b938c28517bf371429260c71e7): * version.in: Bump version to 8.1.50.DATE-git.
2017-04-17Bump version to 8.0.50.DATE-gitJoel Brobecker1-1/+1
Now that the GDB 8.0 branch has been created, we should bump the GDB version accordingly. gdb/ChangeLog: GDB 8.0 branch created (725bf5cf125783c2a7ca4ab63d3768e220bab2db): * version.in: Bump version to 7.99.90.DATE-git.
2016-08-01Bump version to 7.12.50.DATE-git.Joel Brobecker1-1/+1
Now that the GDB 7.12 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 7.12 branch created (41bfcd638a4e0e48b96ce4de2845372dea481322): * version.in: Bump version to 7.12.50.DATE-git.
2016-02-10Bump version to 7.11.50.DATE-git.Joel Brobecker1-1/+1
Now that the GDB 7.11 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 7.11 branch created (9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a): * version.in: Bump version to 7.11.50.DATE-git.
2016-01-05gdb: change version stamp to gitMike Frysinger1-1/+1
2015-07-06Bump version to 7.10.50.DATE-cvs.Joel Brobecker1-1/+1
Now that the GDB 7.10 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 7.10 branch created (66c4b3e8a628a207bc6aafef6af0c4128195f56e): * version.in: Bump version to 7.10.50.DATE-cvs.
2015-01-13Bump version to 7.9.50.DATE-cvs.Joel Brobecker1-1/+1
Now that the GDB 7.9 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 7.9 branch created (92fc2e6978d9a7c8324c7e851dbee59e22ec7a37): * version.in: Bump version to 7.9.50.DATE-cvs.
2014-06-11Bump version to 7.8.50.DATE-cvs.Joel Brobecker1-1/+1
Now that the GDB 7.8 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 7.8 branch created (173373c6f6388171d1d62a217fae90a052395be2): * version.in: Bump version to 7.8.50.DATE-cvs.
2014-01-08Bump version to 7.7.50.DATE-cvs.Joel Brobecker1-1/+1
Now that the GDB 7.7 branch has been created, we can bump the version number. gdb/ChangeLog: GDB 7.7 branch created (79301218fa0f074c5656db0ec8972a5ddcf91fb5): * version.in: Bump version to 7.7.50.DATE-cvs.
2013-06-28move version.in from gdb/common back to gdbTom Tromey1-0/+1
This reverts part of the earlier version.in change. It moves version.in back to the gdb directory. This works around the CVS bug we've found. gdb * Makefile.in (version.c): Use version.in, not common/version.in. * common/create-version.sh: Likewise. * common/version.in: Move... * version.in: ...here. gdb/doc * Makefile.in (version.subst): Use version.in, not common/version.in. * gdbint.texinfo (Versions and Branches, Releasing GDB): Likewise. gdb/gdbserver * Makefile.in (version.c): Use version.in, not common/version.in. sim/common * Make-common.in (version.c): Use version.in, not common/version.in. * create-version.sh: Likewise. sim/ppc: * Make-common.in (version.c): Use version.in, not common/version.in.
2013-06-24don't keep a gdb-specific dateTom Tromey1-1/+0
Right now there are two nightly commits to update a file in the tree with the current date. One commit is for BFD, one is for gdb. It seems unnecessary to me to do this twice. We can make do with a single such commit. This patch changes gdb in a minimal way to reuse the BFD date -- it extracts it from bfd/version.h and changes version.in to use the placeholder string "DATE" for those times when a date is wanted. I propose removing the cron job that updates the version on trunk, and then check in this patch. For release branches, we can keep the cron job, but just tell it to rewrite bfd/version.h. I believe this is a simple change in the crontab -- the script will work just fine on this file. This also moves version.in and version.h into common/, to reflect their shared status; and updates gdbserver to use version.h besides. * common/create-version.sh: New file. * Makefile.in (version.c): Use bfd/version.h, common/version.in, create-version.sh. (HFILES_NO_SRCDIR): Use common/version.h. * version.in: Move to ... * common/version.in: ... here. Replace date with "DATE". * version.h: Move to ... * common/version.h: ... here. gdbserver: * Makefile.in (version.c): Use bfd/version.h, common/version.in, create-version.sh. (version.o): Remove. * gdbreplay.c: Include version.h. (version, host_name): Don't declare. * server.h: Include version.h. (version, host_name): Don't declare. doc: * Makefile.in (POD2MAN1, POD2MAN5): Use version.subst. (GDBvn.texi): Use version.subst. (version.subst): New target. (mostlyclean): Remove version.subst.
2013-06-24*** empty log message ***gdbadmin1-1/+1
2013-06-23*** empty log message ***gdbadmin1-1/+1
2013-06-22*** empty log message ***gdbadmin1-1/+1
2013-06-21*** empty log message ***gdbadmin1-1/+1
2013-06-20*** empty log message ***gdbadmin1-1/+1
2013-06-19*** empty log message ***gdbadmin1-1/+1
2013-06-18*** empty log message ***gdbadmin1-1/+1
2013-06-17*** empty log message ***gdbadmin1-1/+1
2013-06-16*** empty log message ***gdbadmin1-1/+1
2013-06-15*** empty log message ***gdbadmin1-1/+1
2013-06-14*** empty log message ***gdbadmin1-1/+1
2013-06-13*** empty log message ***gdbadmin1-1/+1
2013-06-12*** empty log message ***gdbadmin1-1/+1
2013-06-11*** empty log message ***gdbadmin1-1/+1
2013-06-10*** empty log message ***gdbadmin1-1/+1
2013-06-09*** empty log message ***gdbadmin1-1/+1
2013-06-08*** empty log message ***gdbadmin1-1/+1
2013-06-07*** empty log message ***gdbadmin1-1/+1
2013-06-06*** empty log message ***gdbadmin1-1/+1
2013-06-05*** empty log message ***gdbadmin1-1/+1
2013-06-04*** empty log message ***gdbadmin1-1/+1
2013-06-03*** empty log message ***gdbadmin1-1/+1
2013-06-02*** empty log message ***gdbadmin1-1/+1
2013-06-01*** empty log message ***gdbadmin1-1/+1
2013-05-31*** empty log message ***gdbadmin1-1/+1
2013-05-30*** empty log message ***gdbadmin1-1/+1
2013-05-29*** empty log message ***gdbadmin1-1/+1
2013-05-28*** empty log message ***gdbadmin1-1/+1
2013-05-27*** empty log message ***gdbadmin1-1/+1
2013-05-26*** empty log message ***gdbadmin1-1/+1
2013-05-25*** empty log message ***gdbadmin1-1/+1
2013-05-24*** empty log message ***gdbadmin1-1/+1
2013-05-23*** empty log message ***gdbadmin1-1/+1
2013-05-22*** empty log message ***gdbadmin1-1/+1
2013-05-21*** empty log message ***gdbadmin1-1/+1
2013-05-20*** empty log message ***gdbadmin1-1/+1
generated by cgit v1.1 at 2024-11-29 06:53:00 +0000