From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: mec.gnu@mindspring.com, jingham@apple.com, gdb@sources.redhat.com
Subject: Re: GDB/MI Output Syntax
Date: Thu, 06 Jan 2005 04:48:00 -0000 [thread overview]
Message-ID: <01c4f3aa$Blat.v2.2.2$b4217d20@zahav.net.il> (raw)
In-Reply-To: <20050105232657.GB27494@white> (message from Bob Rossi on Wed, 5 Jan 2005 18:26:57 -0500)
> Date: Wed, 5 Jan 2005 18:26:57 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: jingham@apple.com, gdb@sources.redhat.com
>
> 1. will the grammar and bison syntax be good to document so that others can see it?
I think it's enough to point to the grammar definition file in the MI
docs. There's no need to do more in the docs; the grammar should
document itself.
> 3. Would a patch like this be acceptable even if it was accomplished?
Why not?
next prev parent reply other threads:[~2005-01-06 4:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1093622671.2836.ezmlm@sources.redhat.com>
2004-08-27 17:56 ` Jim Ingham
2004-08-27 19:12 ` Michael Chastain
2005-01-05 23:27 ` Bob Rossi
2005-01-06 4:48 ` Eli Zaretskii [this message]
2005-01-06 23:31 ` Bob Rossi
2005-01-07 0:36 ` Jim Ingham
2005-01-07 1:12 ` Bob Rossi
2005-01-07 3:12 ` Russell Shaw
2005-01-11 19:35 ` Bob Rossi
2005-01-13 2:23 ` Bob Rossi
2005-01-13 2:46 ` Intrusive GDB Symbol Lookup when debugging remotely David Steven Trollope
2005-01-22 4:25 ` Dave Trollope
2005-01-24 19:48 ` Andrew Cagney
2005-01-24 19:54 ` David Steven Trollope
2005-03-18 16:29 ` Linux Realtime Scheduling Option David Steven Trollope
2005-03-18 18:12 ` Daniel Jacobowitz
2005-03-21 19:21 ` David Steven Trollope
2005-03-21 19:33 ` Daniel Jacobowitz
2005-03-22 3:04 ` Dave Trollope
2005-03-22 4:06 ` Daniel Jacobowitz
2005-01-06 0:28 GDB/MI Output Syntax Paul Schlie
2005-01-06 0:32 ` Kip Macy
2005-01-06 0:49 ` Paul Schlie
2005-01-06 1:10 ` Bob Rossi
2005-01-06 1:36 ` Paul Schlie
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 15:44 Bob Rossi
2004-08-25 15:57 ` Michael Chastain
2004-08-25 19:37 ` Bob Rossi
2004-08-26 14:01 ` Michael Chastain
2004-08-26 18:31 ` Bob Rossi
2004-08-26 20:44 ` Michael Chastain
2004-08-26 20:52 ` Keith Seitz
2004-08-26 22:16 ` Michael Chastain
2004-08-26 22:03 ` Bob Rossi
2004-08-26 23:06 ` Michael Chastain
2004-08-26 21:13 ` Andrew Cagney
2004-08-26 21:25 ` Bob Rossi
2004-08-26 22:46 ` Michael Chastain
2004-08-27 10:14 ` Eli Zaretskii
2004-08-26 22:41 ` Michael Chastain
2004-08-24 3:12 Bob Rossi
2004-08-24 4:15 ` Michael Chastain
2004-08-24 12:30 ` Bob Rossi
2004-08-24 12:50 ` Michael Chastain
2004-08-24 18:59 ` Andrew Cagney
2004-08-24 19:07 ` Bob Rossi
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='01c4f3aa$Blat.v2.2.2$b4217d20@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.com \
--cc=mec.gnu@mindspring.com \
/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