1. 31 Jan, 2018 1 commit
  2. 12 Jan, 2018 2 commits
  3. 05 Jan, 2018 1 commit
  4. 17 Apr, 2017 1 commit
    • Joel Brobecker's avatar
      Bump version to 8.0.50.DATE-git · 8bb57231
      Joel Brobecker authored
      Now that the GDB 8.0 branch has been created, we should bump
      the GDB version accordingly.
      
      gdb/ChangeLog:
      
      	GDB 8.0 branch created (725bf5cf):
      	* version.in: Bump version to 7.99.90.DATE-git.
      8bb57231
  5. 01 Aug, 2016 1 commit
  6. 10 Feb, 2016 1 commit
  7. 06 Jan, 2016 1 commit
  8. 06 Jul, 2015 1 commit
  9. 13 Jan, 2015 1 commit
  10. 11 Jun, 2014 1 commit
  11. 08 Jan, 2014 1 commit
  12. 28 Jun, 2013 1 commit
    • Tom Tromey's avatar
      move version.in from gdb/common back to gdb · d6c2da54
      Tom Tromey authored
      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.
      d6c2da54
  13. 24 Jun, 2013 1 commit
    • Tom Tromey's avatar
      don't keep a gdb-specific date · 01208463
      Tom Tromey authored
      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.
      01208463