Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [rfa, doc] Remove warning about "unstable" Target Descriptions format
Date: Thu, 16 Jun 2011 09:15:00 -0000	[thread overview]
Message-ID: <201106160915.p5G9FchO026070@d06av02.portsmouth.uk.ibm.com> (raw)

Hello,

it was just pointed out to me that the documentation about
Target Descriptions still shows a prominent warning that the
format of those description is still "under active development"
and may change between releases.

Now while this may have been true when the warning was originally
added (over 4 years ago), at this point I'd certainly consider
the basic format to be stable (of course, additional features may
get supported via new XML elements over time, but that does not
affect backward compatibilty).

As the continued presence of that warning may actually have the
effect of making people reluctant to implement target descriptions
in remote agents, it seems counterproductive to keep the warning.

The patch below removes the warning from the doc.

Any comments?

Bye,
Ulrich


ChangeLog:

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

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.841
diff -u -p -r1.841 gdb.texinfo
--- gdb/doc/gdb.texinfo	3 Jun 2011 15:32:44 -0000	1.841
+++ gdb/doc/gdb.texinfo	16 Jun 2011 09:00:57 -0000
@@ -36368,10 +36368,6 @@ The formal DTD for the traceframe info f
 @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
-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


             reply	other threads:[~2011-06-16  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  9:15 Ulrich Weigand [this message]
2011-06-16 14:45 ` Tom Tromey
2011-06-29 12:28   ` Ulrich Weigand
2011-06-29 16:18     ` Eli Zaretskii
2011-06-29 16:30       ` Ulrich Weigand

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=201106160915.p5G9FchO026070@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.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