This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] don't keep a gdb-specific date
- From: Pedro Alves <palves at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 19 Jun 2013 18:35:27 +0100
- Subject: Re: [PATCH] don't keep a gdb-specific date
- References: <1371662226-10926-1-git-send-email-tromey at redhat dot com>
On 06/19/2013 06:17 PM, Tom Tromey wrote:
> 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 bfdver.h and changes version.in to use the
> placeholder string "DATE" for those times when a date is wanted.
>
> I remove 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.
What about gdbserver? I suspect it'll print literal
"7.6.50.DATE-cvs" as version date with this patch.
--
Pedro Alves