public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [release/branch 2/2] Set development mode to "off" by default.
Date: Sun, 20 Mar 2022 09:19:40 +0400	[thread overview]
Message-ID: <20220320051940.106176-3-brobecker@adacore.com> (raw)
In-Reply-To: <20220320051940.106176-1-brobecker@adacore.com>

This is done by setting the "development" variable to "false"
in bfd/development.sh.
---
 bfd/development.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bfd/development.sh b/bfd/development.sh
index d7b944d181..f4f15e04bf 100644
--- a/bfd/development.sh
+++ b/bfd/development.sh
@@ -16,7 +16,7 @@
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
 # Controls whether to enable development-mode features by default.
-development=true
+development=false
 
 # Indicate whether this is a release branch.
 experimental=true
-- 
2.32.0


  parent reply	other threads:[~2022-03-20  5:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20  5:19 FYI/BRANCH: Patches applied to branch gdb-12-branch Joel Brobecker
2022-03-20  5:19 ` [release/branch 1/2] Bump version to 12.0.90.DATE-git Joel Brobecker
2022-03-20  5:19 ` Joel Brobecker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-18  4:39 FYI/BRANCH: Patches applied to branch gdb-13-branch Joel Brobecker
2022-12-18  4:39 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2021-07-03 17:53 FYI/BRANCH: Patches applied to branch gdb-11-branch Joel Brobecker
2021-07-03 17:53 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2019-12-11 20:46 FYI/BRANCH: Patches applied to branch gdb-9-branch Joel Brobecker
2019-12-11 20:46 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2019-02-27  5:01 FYI/BRANCH: Patches applied to branch gdb-8.3-branch Joel Brobecker
2019-02-27  5:01 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2018-07-04 15:49 FYI/BRANCH: Patches applied to branch gdb-8.2-branch Joel Brobecker
2018-07-04 15:49 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2016-08-01 15:29 FYI/BRANCH: Patches applied to branch gdb-7.12-branch Joel Brobecker
2016-08-01 15:29 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2016-02-10  3:29 FYI/BRANCH: Patches applied to branch gdb-7.11-branch Joel Brobecker
2016-02-10  3:29 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2015-07-06 20:03 FYI/BRANCH: Patches applied to branch gdb-7.10-branch Joel Brobecker
2015-07-06 20:03 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2015-01-13 12:26 FYI/BRANCH: Patches applied to branch gdb-7.9-branch Joel Brobecker
2015-01-13 12:26 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2014-06-11 16:53 [release/branch 1/2] Bump version to 7.7.90.DATE-cvs Joel Brobecker
2014-06-11 16:53 ` [release/branch 2/2] Set development mode to "off" by default Joel Brobecker
2014-01-08  9:42 FYI/BRANCH: Patches applied to branch gdb-7.7-branch Joel Brobecker
2014-01-08  9:42 ` [release/branch 2/2] Set development mode to "off" by default 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=20220320051940.106176-3-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).