From 6f5def7d9ee6b0f09cefb41a55c72aff77787cfe Mon Sep 17 00:00:00 2001
From: Ulrich Weigand <uweigand@de.ibm.com>
Date: Wed, 29 Jun 2011 16:28:22 +0000
Subject: [PATCH] * gdb.texinfo (Target Description): Remove warning
about possibly unstable format.
---
gdb/doc/ChangeLog | 5 +++++
gdb/doc/gdb.texinfo | 4 ----
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 7366ad99a27..bdff2462de3 100644
--- 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 3a705c2c575..ca2b4d58749 100644
--- 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