* gdb.texinfo (Target Description): Remove warning about

	possibly unstable format.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 7366ad99a274a6843c520db9df4418944eb29a5d..bdff2462de33553ca5b6320c96ed3fe3ed594a00 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2011-06-29  Ulrich Weigand  <ulrich.weigand@linaro.org>
+
+       * gdb.texinfo (Target Description): Remove warning about
+       possibly unstable format.
+
 2011-06-03  Tom Tromey  <tromey@redhat.com>
 
        * gdb.texinfo (GDB/MI Async Records): Document 'exit-code' field.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 3a705c2c5757789c1eab2442fd1b72127b1035ba..ca2b4d5874971ae25ab5b0dbf8fe336a3da5ba65 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -36368,10 +36368,6 @@ The formal DTD for the traceframe info format is given below:
 @appendix Target Descriptions
 @cindex target descriptions
 
-@strong{Warning:} target descriptions are still under active development,
-and the contents and format may change between @value{GDBN} releases.
-The format is expected to stabilize in the future.
-
 One of the challenges of using @value{GDBN} to debug embedded systems
 is that there are so many minor variants of each processor
 architecture in use.  It is common practice for vendors to start with