Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stanshebs@earthlink.net,  gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Sat, 23 Jun 2007 20:51:00 -0000	[thread overview]
Message-ID: <467D87E6.2000908@eagercon.com> (raw)
In-Reply-To: <u3b0ipi69.fsf@gnu.org>

Eli Zaretskii wrote:
>> Date: Sat, 23 Jun 2007 12:08:40 -0700
>> From: Michael Eager <eager@eagercon.com>
>> CC:  gdb@sources.redhat.com
>>
>> I'm assuming that the XML target description in the docs is similarly
>> incomplete and/or obsolete.
> 
> On the contrary: it is relatively very new and its documentation is
> supposed to be quite complete (at least as far as the manuals go; if
> you are talking about the code, that's a different matter).  So if you
> find some portions of its documentation unclear or incomplete, please
> point that out.

The doc refers to a non-existent DTD file which is supposed to
describe the XML target description annex.  I assumed it was obsolete.

It's not clear whether this is the same annex referenced in target.c.

>> There seems to be a fair amount of cruft in the code, and
>> even more in the documentation.  Sigh.
> 
> I'm sure we will welcome patches.

I'd be happy to.  It's not easy to create patches when it's
unclear whether the doc is out of date or the source hasn't
caught up yet.  There are many areas where the docs are out
sync with the source.

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


  reply	other threads:[~2007-06-23 20:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23 18:01 Michael Eager
2007-06-23 18:57 ` Stan Shebs
2007-06-23 19:08   ` Michael Eager
2007-06-23 19:47     ` Eli Zaretskii
2007-06-23 20:51       ` Michael Eager [this message]
2007-06-23 21:23         ` Daniel Jacobowitz
2007-06-23 21:40           ` Michael Eager
2007-06-24  2:58             ` Eli Zaretskii
2007-06-24  4:32               ` Michael Eager
2007-06-25 18:03     ` Jim Blandy
2007-06-25 18:39       ` Michael Eager
2007-06-25 19:10         ` Jim Blandy
2007-06-25 19:26           ` Paul Koning
2007-06-25 19:32             ` Daniel Jacobowitz
2007-06-25 19:38               ` Robert Dewar
2007-06-25 19:48                 ` Paul Koning
2007-06-25 20:09                   ` Michael Eager
2007-06-25 20:40                     ` Robert Dewar
2007-06-25 20:47                       ` Robert Dewar
2007-06-25 20:31                 ` Eli Zaretskii
2007-06-25 20:44                   ` Robert Dewar
2007-06-25 21:00                     ` Eli Zaretskii
2007-06-25 21:03                       ` Robert Dewar
2007-06-25 21:06                         ` Robert Dewar
2007-06-26 18:34                   ` Markus Deuling
2007-06-26 18:36                     ` Robert Dewar
2007-06-26 21:55                     ` Jim Blandy
2007-06-26 22:14                       ` Nick Roberts
2007-06-26 23:26                       ` Robert Dewar
2007-06-26 23:39                         ` Joel Brobecker
2007-06-26 23:43                           ` Robert Dewar
2007-06-27  0:32                             ` Jim Blandy
2007-06-27  0:42                               ` Robert Dewar
2007-06-27  3:22                                 ` Eli Zaretskii
2007-06-27  0:23                       ` Michael Eager
2007-06-25 20:42             ` Eli Zaretskii
2007-06-25 20:23           ` Eli Zaretskii
2007-06-25 21:52             ` Jim Blandy
2007-06-26  1:04               ` Paul Koning
2007-06-25 20:37         ` Eli Zaretskii
2007-06-25 20:15       ` Eli Zaretskii

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=467D87E6.2000908@eagercon.com \
    --to=eager@eagercon.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=stanshebs@earthlink.net \
    /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