From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Bob Rossi <bob_rossi@cox.net>, Eli Zaretskii <eliz@gnu.org>,
ghost@cs.msu.su, gdb-patches@sources.redhat.com
Subject: Re: CLI and GDB/MI documentation patch
Date: Sat, 13 May 2006 16:04:00 -0000 [thread overview]
Message-ID: <20060513154631.GA4941@nevyn.them.org> (raw)
In-Reply-To: <17510.62256.102468.268003@kahikatea.snap.net.nz>
On Sun, May 14, 2006 at 09:06:56PM +1200, Nick Roberts wrote:
> AFAICS the only changes to MI since 6.4 have been to add the fullname field
> to breakpoint related commands and to generate an error record for directly
> entered CLI commands. I think we only need to bump the number when an
> incompatible change change is made that will break existing front ends.
Right. I have at least one such change in mind - I posted about the
mess of quoting and backslash processing on gdb@ some time ago though I
have no idea when I'll have time to get back to it. The asynchronous
changes you've been working with may also require an MI level bump.
> break with the new level). We did start to talk about what changes could be
> made within one level: new commands, extra fields etc which I think we need to
> document so that developers know what to expect. I think at some stage we
> should also document our thoughts changing MI level.
I invite you :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-13 15:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 12:44 Nick Roberts
2006-05-12 14:19 ` Eli Zaretskii
2006-05-12 16:42 ` Bob Rossi
2006-05-12 22:14 ` Nick Roberts
2006-05-12 22:19 ` Bob Rossi
2006-05-13 9:13 ` Nick Roberts
2006-05-13 16:04 ` Daniel Jacobowitz [this message]
2006-05-30 15:59 ` {PATCH] MI Doco [was Re: CLI and GDB/MI...] Nick Roberts
2006-05-31 1:20 ` Eli Zaretskii
2006-05-31 3:15 ` Nick Roberts
2006-05-31 13:02 ` Eli Zaretskii
2006-05-31 22:04 ` Nick Roberts
2006-05-31 23:17 ` Daniel Jacobowitz
2006-06-01 7:24 ` Eli Zaretskii
2006-06-01 13:09 ` Daniel Jacobowitz
2006-05-31 15:33 ` Bob Rossi
2006-05-31 22:11 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 1:16 CLI and GDB/MI documentation patch Bob Rossi
2006-05-12 7:53 ` Eli Zaretskii
2006-05-12 8:14 ` Vladimir Prus
2006-05-12 11:30 ` Eli Zaretskii
2006-05-12 13:56 ` Bob Rossi
2006-05-12 12:49 ` Daniel Jacobowitz
2006-05-12 12:54 ` Daniel Jacobowitz
2006-05-12 13:58 ` Eli Zaretskii
2006-05-12 14:02 ` Daniel Jacobowitz
2006-05-12 14:10 ` Bob Rossi
2006-05-12 18:32 ` Eli Zaretskii
2006-05-12 18:37 ` Eli Zaretskii
2006-05-12 18:55 ` Daniel Jacobowitz
2006-05-12 19:01 ` Eli Zaretskii
2006-05-12 19:16 ` Daniel Jacobowitz
2006-05-12 19:51 ` Bob Rossi
2006-05-13 9:28 ` Eli Zaretskii
2006-05-15 15:50 ` Daniel Jacobowitz
2006-05-12 20:26 ` PAUL GILLIAM
2006-05-13 8:45 ` Eli Zaretskii
2006-05-12 12:59 ` Bob Rossi
2006-05-12 14:12 ` Eli Zaretskii
2006-05-12 14:30 ` Bob Rossi
2006-05-12 18:28 ` Eli Zaretskii
2006-05-12 19:19 ` Bob Rossi
2006-05-13 8:09 ` Eli Zaretskii
2006-05-13 11:02 ` Bob Rossi
2006-05-13 14:29 ` Eli Zaretskii
2006-05-29 19:05 ` Bob Rossi
2006-05-30 7:17 ` 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=20060513154631.GA4941@nevyn.them.org \
--to=drow@false.org \
--cc=bob_rossi@cox.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/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