X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=binutils%2FREADME;h=6633792d87b350cc9d08b30a66e8bf4c75154467;hb=fd31a1711cf8813860353e9196cdfdfbbdd749d4;hp=e51b2a2cb55ddfaa76b9cbe17ceecaa48650912a;hpb=1b577b00bda93731de384fefea094f3b78d96ee0;p=deliverable%2Fbinutils-gdb.git

diff --git a/binutils/README b/binutils/README
index e51b2a2cb5..6633792d87 100644
--- a/binutils/README
+++ b/binutils/README
@@ -18,7 +18,7 @@ Unpacking and Installation -- quick overview
 
 When you unpack the binutils archive file, you will get a directory
 called something like `binutils-XXX', where XXX is the number of the
-release.  (Probably 2.11.2 or higher).  This directory contains
+release.  (Probably 2.12 or higher).  This directory contains
 various files and sub-directories.  Most of the files in the top
 directory are for information and for configuration.  The actual
 source code is in sub-directories.
@@ -110,7 +110,7 @@ the ranlib program in order to build the distribution.
 Porting
 =======
 
-Binutils-2.11 supports many different architectures, but there
+Binutils-2.12 supports many different architectures, but there
 are many more not supported, including some that were supported
 by earlier versions.  We are hoping for volunteers to improve this
 situation.
@@ -118,14 +118,14 @@ situation.
 The major effort in porting binutils to a new host and/or target
 architecture involves the BFD library.  There is some documentation
 in ../bfd/doc.  The file ../gdb/doc/gdbint.texinfo (distributed
-with gdb-4.x) may also be of help.
+with gdb-5.x) may also be of help.
 
 Reporting bugs
 ==============
 
 Send bug reports and patches to:
 
-   bug-gnu-utils@gnu.org.
+   bug-binutils@gnu.org.
 
 Always mention the version number you are running; this is printed by
 running any of the binutils with the --version option.  We appreciate