[binutils-gdb] Move s390-* target to the obsolete list. Update README-how-to-make-a-relese to reference the future

[Nick Clifton]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6e9d2f4fada48f9ac0902150fc17cf3649a208c2

commit 6e9d2f4fada48f9ac0902150fc17cf3649a208c2
Author: Nick Clifton <nickc@redhat.com>
Date:   Sun Jul 26 19:28:33 2026 +0100

    Move s390-* target to the obsolete list.  Update README-how-to-make-a-relese to reference the future 2.48 release.

Diff:
---
 bfd/config.bfd                        |  2 +-
 binutils/README-how-to-make-a-release | 29 +++++++++++++++--------------
 2 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/bfd/config.bfd b/bfd/config.bfd
index 632f34312d4..8eb2131128d 100644
--- a/bfd/config.bfd
+++ b/bfd/config.bfd
@@ -48,7 +48,6 @@ targ_underscore=no
 
 # Catch obsolete configurations.
 case $targ in
- s390-* | \
  null)
     if test "x$enable_obsolete" != xyes; then
       echo "*** Configuration $targ is obsolete." >&2
@@ -164,6 +163,7 @@ case $targ in
  or32-*-* | \
  powerpc-*-lynxos* | powerpc-*-windiss* | \
  powerpcle-*-pe | powerpcle-*-winnt* | powerpcle-*-cygwin* | \
+ s390-* | \
  sh*-*-netbsdaout* | \
  sh*-*-symbianelf* | sh5*-*-* | sh64*-*-* | \
  sparc*-*-*aout* | \
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 55f7892a9ea..6aa02da8aa7 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -286,9 +286,10 @@ How to create the release.
 
   21. a. Update the release number in bfd/version.m4 on the release
          branch to a whole new minor version number, without a point
-         value.  Eg "2.46.90" becomes "2.47".  NB/ Not: "2.47.00"
+         value.  Eg "2.47.90" becomes "2.48".  NB/ Not: "2.48.00"
 
-      b. Change bfd/development.sh to set all values to "false".
+      b. Change bfd/development.sh to set all values (ie 'development'
+         and 'experimental') to "false". 
 
       c. Regenerate the configure and makefiles.  And *info* files.
 
@@ -316,7 +317,7 @@ How to create the release.
       e. Commit.
 
 	   git add .
-           git commit -m "This is the 2.46 release"
+           git commit -m "This is the 2.48 release"
 	   git push
 	   
   22. Check that your file creation mask will create the
@@ -414,16 +415,16 @@ How to create the release.
 	    git tag -a <TAG> -u <Your Key> -m "Your message"
 	    
 	  eg:
-	    git tag -a binutils-2_47 -u DD9E3C4F      <=== Be careful to get the tag right
+	    git tag -a binutils-2_48 -u DD9E3C4F      <=== Be careful to get the tag right
 	  or:
-	    git tag -a binutils-2_47 -u DD9E3C4F -m "Official GNU Binutils 2.46 release"
+	    git tag -a binutils-2_48 -u DD9E3C4F -m "Official GNU Binutils 2.48 release"
 
         NB/ If you do sign the binaries make sure to use a key
 	that has been published with the FSF.
 
         Then push the release:
 
-	    git push origin binutils-2_47
+	    git push origin binutils-2_48
 
         If you get an error message along the lines of:
 	  "Invalid revision range ..."
@@ -431,7 +432,7 @@ How to create the release.
 
   27.  Upload the tarballs to ftp.gnu.org.
 
-          gnupload --to ftp.gnu.org:binutils binutils*47*.tar.*
+          gnupload --to ftp.gnu.org:binutils binutils*48*.tar.*
 
         Be prepared to provide the password for the key, if you
 	signed the binaries.
@@ -451,8 +452,8 @@ How to create the release.
 
        sftp sourceware.org
          cd /sourceware/ftp/pub/binutils/releases
- 	 put binutils*47*.tar.*
- 	 chmod 644 binutils*47*.tar.*
+ 	 put binutils*48*.tar.*
+ 	 chmod 644 binutils*48*.tar.*
 	 quit
 
   29. Update web pages.  For sourceware.org:
@@ -464,8 +465,8 @@ How to create the release.
       Create a new docs sub-directory and move into it:
 
         cd binutils-htdocs
-	mkdir docs-2.46
-        cd docs-2.46
+	mkdir docs-2.48
+        cd docs-2.48
 	
       Copy the index.html from the previous release
 
@@ -514,7 +515,7 @@ How to create the release.
 
          cd ..     [Should now be in be in binutils-htdocs/ ]
 	 rm docs
-	 ln -s docs-2.47 docs
+	 ln -s docs-2.48 docs
 	 
       Edit index.html file to change the links to point to the new
       release, mention any new features, update dates and so on.
@@ -525,9 +526,9 @@ How to create the release.
 
       Add the new directories and files, commit and push the changes:
 
-        git add docs-2.47
+        git add docs-2.48
         git add .
-        git commit -m"Update documenation for the 2.47 release"
+        git commit -m"Add documenation for the 2.48 release"
 	git push