From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: MI -break-info command issues
Date: Fri, 27 Jan 2006 17:41:00 -0000 [thread overview]
Message-ID: <uacdhegtf.fsf@gnu.org> (raw)
In-Reply-To: <drdgkk$qt1$1@sea.gmane.org> (message from Vladimir Prus on Fri, 27 Jan 2006 19:09:56 +0300)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Fri, 27 Jan 2006 19:09:56 +0300
>
> It would be good, though, if MI docs contained some introduction
> chapter that would state this policy.
I agree, and will gladly accept patches to this effect.
next prev parent reply other threads:[~2006-01-27 17:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 14:22 Vladimir Prus
2006-01-24 14:48 ` Bob Rossi
2006-01-24 15:02 ` Vladimir Prus
2006-01-24 21:24 ` Eli Zaretskii
2006-01-24 23:35 ` Bob Rossi
2006-01-25 16:05 ` Vladimir Prus
2006-01-25 19:42 ` Eli Zaretskii
2006-01-26 12:09 ` Vladimir Prus
2006-01-26 20:48 ` Eli Zaretskii
2006-01-27 12:16 ` Vladimir Prus
2006-01-27 14:55 ` Eli Zaretskii
2006-01-27 15:00 ` Bob Rossi
2006-01-27 15:12 ` Vladimir Prus
2006-01-27 15:48 ` Daniel Jacobowitz
2006-01-27 15:51 ` Vladimir Prus
2006-01-27 16:11 ` Daniel Jacobowitz
2006-01-27 16:01 ` Daniel Jacobowitz
2006-01-27 16:44 ` Vladimir Prus
2006-01-27 17:00 ` Bob Rossi
2006-02-10 12:03 ` Documenting MI stability (Was: MI -break-info command issues) Vladimir Prus
2006-01-27 17:41 ` Eli Zaretskii [this message]
2006-01-27 17:16 ` MI -break-info command issues Eli Zaretskii
2006-01-27 17:53 ` Bob Rossi
2006-01-28 14:48 ` Eli Zaretskii
2006-01-27 17:12 ` Eli Zaretskii
2006-03-17 17:07 ` -data-read-memory docs (Was: MI -break-info command issues) Vladimir Prus
2006-03-18 11:26 ` 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=uacdhegtf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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