Commit Graph

4385 Commits

Author SHA1 Message Date
Mike Frysinger
bf69ad5a18 gdb: change version stamp to git 2016-01-05 23:23:52 -05:00
Joel Brobecker
f2232bea32 Bump version to 7.10.50.DATE-cvs.
Now that the GDB 7.10 branch has been created, we can
bump the version number.

gdb/ChangeLog:

	GDB 7.10 branch created (66c4b3e8a6):
	* version.in: Bump version to 7.10.50.DATE-cvs.
2015-07-06 12:58:29 -07:00
Joel Brobecker
b4cfe7f88e Bump version to 7.9.50.DATE-cvs.
Now that the GDB 7.9 branch has been created, we can
bump the version number.

gdb/ChangeLog:

	GDB 7.9 branch created (92fc2e6978):
	* version.in: Bump version to 7.9.50.DATE-cvs.
2015-01-13 16:16:07 +04:00
Joel Brobecker
71a55bdf7d Bump version to 7.8.50.DATE-cvs.
Now that the GDB 7.8 branch has been created, we can
bump the version number.

gdb/ChangeLog:

	GDB 7.8 branch created (173373c6f6):
	* version.in: Bump version to 7.8.50.DATE-cvs.
2014-06-11 18:37:55 +02:00
Joel Brobecker
16dfbded4c Bump version to 7.7.50.DATE-cvs.
Now that the GDB 7.7 branch has been created, we can
bump the version number.

gdb/ChangeLog:

	GDB 7.7 branch created (79301218fa):
	* version.in: Bump version to 7.7.50.DATE-cvs.
2014-01-08 13:25:28 +04:00
Tom Tromey
d6c2da5446 move version.in from gdb/common back to gdb
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-28 18:59:51 +00:00
Tom Tromey
0120846339 don't keep a gdb-specific date
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 15:06:27 +00:00
gdbadmin
5ba23a3fa1 *** empty log message *** 2013-06-24 00:00:02 +00:00
gdbadmin
38d08085af *** empty log message *** 2013-06-23 00:00:02 +00:00
gdbadmin
a913933049 *** empty log message *** 2013-06-22 00:00:32 +00:00
gdbadmin
87f0aee73d *** empty log message *** 2013-06-21 00:00:32 +00:00
gdbadmin
181ff4a40d *** empty log message *** 2013-06-20 00:00:32 +00:00
gdbadmin
de21c15716 *** empty log message *** 2013-06-19 00:00:02 +00:00
gdbadmin
9f9b731fe3 *** empty log message *** 2013-06-18 00:00:32 +00:00
gdbadmin
0b266b4186 *** empty log message *** 2013-06-17 00:00:33 +00:00
gdbadmin
77c7972fa8 *** empty log message *** 2013-06-16 00:00:03 +00:00
gdbadmin
6da195136d *** empty log message *** 2013-06-15 00:00:03 +00:00
gdbadmin
1a39a68ee7 *** empty log message *** 2013-06-14 00:00:32 +00:00
gdbadmin
479a1f0a6f *** empty log message *** 2013-06-13 00:00:32 +00:00
gdbadmin
a9bb8c343e *** empty log message *** 2013-06-12 00:00:02 +00:00
gdbadmin
37f134cb96 *** empty log message *** 2013-06-11 00:00:02 +00:00
gdbadmin
a7cfa99ecf *** empty log message *** 2013-06-10 00:00:32 +00:00
gdbadmin
65b8e0e1ca *** empty log message *** 2013-06-09 00:00:32 +00:00
gdbadmin
8d3caaf0a7 *** empty log message *** 2013-06-08 00:00:02 +00:00
gdbadmin
e808d707b4 *** empty log message *** 2013-06-07 00:00:03 +00:00
gdbadmin
b997f18b20 *** empty log message *** 2013-06-06 00:00:02 +00:00
gdbadmin
256b85c25e *** empty log message *** 2013-06-05 00:00:33 +00:00
gdbadmin
0e8faa7b6e *** empty log message *** 2013-06-04 00:00:32 +00:00
gdbadmin
2590d1455c *** empty log message *** 2013-06-03 00:00:03 +00:00
gdbadmin
e55608f4cc *** empty log message *** 2013-06-02 00:00:32 +00:00
gdbadmin
bb8779ef82 *** empty log message *** 2013-06-01 00:00:02 +00:00
gdbadmin
e8de40a833 *** empty log message *** 2013-05-31 00:00:32 +00:00
gdbadmin
c0f316436d *** empty log message *** 2013-05-30 00:00:32 +00:00
gdbadmin
177565ddef *** empty log message *** 2013-05-29 00:00:02 +00:00
gdbadmin
18e17b047d *** empty log message *** 2013-05-28 00:00:02 +00:00
gdbadmin
0513b0a3e8 *** empty log message *** 2013-05-27 00:00:03 +00:00
gdbadmin
89ca6a248b *** empty log message *** 2013-05-26 00:00:02 +00:00
gdbadmin
b5cc0fabb4 *** empty log message *** 2013-05-25 00:00:03 +00:00
gdbadmin
e6ec244956 *** empty log message *** 2013-05-24 00:00:02 +00:00
gdbadmin
5fd133faea *** empty log message *** 2013-05-23 00:00:03 +00:00
gdbadmin
6415af12e6 *** empty log message *** 2013-05-22 00:00:03 +00:00
gdbadmin
a825696a06 *** empty log message *** 2013-05-21 00:00:32 +00:00
gdbadmin
fdc2322aef *** empty log message *** 2013-05-20 00:00:02 +00:00
gdbadmin
2f2fb5e626 *** empty log message *** 2013-05-19 00:00:33 +00:00
gdbadmin
3e68617657 *** empty log message *** 2013-05-18 00:00:02 +00:00
gdbadmin
4bebc771c7 *** empty log message *** 2013-05-17 00:00:32 +00:00
gdbadmin
38d80a64fb *** empty log message *** 2013-05-16 00:00:02 +00:00
gdbadmin
fba526b6fb *** empty log message *** 2013-05-15 00:00:32 +00:00
gdbadmin
ce355ebab0 *** empty log message *** 2013-05-14 00:00:02 +00:00
gdbadmin
8444d6e5fb *** empty log message *** 2013-05-13 00:00:32 +00:00