Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: CLI and GDB/MI documentation patch
Date: Fri, 12 May 2006 08:14:00 -0000	[thread overview]
Message-ID: <e41g34$hhg$1@sea.gmane.org> (raw)
In-Reply-To: <u1wuz8yrc.fsf@gnu.org>

Eli Zaretskii wrote:

>> Date: Thu, 11 May 2006 21:17:30 -0400
>> From: Bob Rossi <bob_rossi@cox.net>
>> 
>> I hope this looks correct. Please let me know otherwise. I think it's
>> an improvement over what is there now, and could save others valuable
>> research time.
> 
> Sorry, I don't understand what you are trying to say here, exactly.
> Explaining why we did something in the past does not belong in the
> manual (except maybe in a footnote, if it is _very_ important to
> mention history).
> 
> Perhaps I wasn't following the thread closely enough, so I missed
> something important.  Can you state what information is missing from
> the current text in this section?  You say above that the changes
> ``could save others valuable research time''--what did you need to
> research, and why, and what did you find that wasn't described in the
> manual?

I'd agree with Eli that the proposed text sounds a bit like history, but it
documents some important points:

- That you can type CLI commands into MI, and this is not longer considered
  to work just by accident
- That typing CLI command has the same effect as -interpreter-exec console
- That CLI command don't produce async notifications

Those points are important to have documented, IMO.

- Volodya




  reply	other threads:[~2006-05-12  8:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  1:16 Bob Rossi
2006-05-12  7:53 ` Eli Zaretskii
2006-05-12  8:14   ` Vladimir Prus [this message]
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
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

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='e41g34$hhg$1@sea.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.redhat.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