From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [release/HEAD 1/2] Bump version to 17.0.50.DATE-git.
Date: Sun, 29 Dec 2024 07:01:13 +0400 [thread overview]
Message-ID: <20241229030114.261481-2-brobecker@adacore.com> (raw)
In-Reply-To: <20241229030114.261481-1-brobecker@adacore.com>
Now that the GDB 16 branch has been created,
this commit bumps the version number in gdb/version.in to
17.0.50.DATE-git
For the record, the GDB 16 branch was created
from commit ee29a3c4ac7adc928ae6ed1fed3b59c940a519a4.
Also, as a result of the version bump, the following changes
have been made in gdb/testsuite:
* gdb.base/default.exp: Change $_gdb_major to 17.
---
gdb/testsuite/gdb.base/default.exp | 2 +-
gdb/version.in | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.base/default.exp b/gdb/testsuite/gdb.base/default.exp
index b1cf957887b..bbc95aa0539 100644
--- a/gdb/testsuite/gdb.base/default.exp
+++ b/gdb/testsuite/gdb.base/default.exp
@@ -691,7 +691,7 @@ set show_conv_list \
{$_gdb_maint_setting = <internal function _gdb_maint_setting>} \
{$_gdb_setting_str = <internal function _gdb_setting_str>} \
{$_gdb_setting = <internal function _gdb_setting>} \
- {$_gdb_major = 16} \
+ {$_gdb_major = 17} \
{$_gdb_minor = 1} \
{$_shell_exitsignal = void} \
{$_shell_exitcode = 0} \
diff --git a/gdb/version.in b/gdb/version.in
index 48f1b847670..75e06a83cc9 100644
--- a/gdb/version.in
+++ b/gdb/version.in
@@ -1 +1 @@
-16.0.50.DATE-git
\ No newline at end of file
+17.0.50.DATE-git
\ No newline at end of file
--
2.34.1
next prev parent reply other threads:[~2024-12-29 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 3:01 FYI/HEAD: Patches applied to branch master Joel Brobecker
2024-12-29 3:01 ` Joel Brobecker [this message]
2024-12-29 3:01 ` [release/HEAD 2/2] Update gdb/NEWS after GDB 16 branch creation Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241229030114.261481-2-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox