From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] MI non-stop and multiprocess docs.
Date: Thu, 13 Nov 2008 13:42:00 -0000 [thread overview]
Message-ID: <u63msp8ie.fsf@gnu.org> (raw)
In-Reply-To: <200811130016.20863.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Thu, 13 Nov 2008 00:16:20 +0300
> Cc: gdb-patches@sources.redhat.com
>
> > "General Aspects of Interacting with GDB/MI"?
>
> That's heavy, I think.
How do you mean "heavy"?
If you object to "design" then what about:
>
> - "GDB/MI General Overview", or
> - "GDB/MI General Concepts",
Again, I don't think that's what the section is about.
But we are arguing too long about something that's not important
enough to argue about.
next prev parent reply other threads:[~2008-11-13 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 19:15 Vladimir Prus
2008-11-04 21:22 ` Eli Zaretskii
2008-11-08 12:05 ` Eli Zaretskii
2008-11-12 20:37 ` Vladimir Prus
2008-11-12 20:44 ` Eli Zaretskii
2008-11-12 20:47 ` Vladimir Prus
2008-11-13 4:15 ` Eli Zaretskii
2008-11-13 5:31 ` Vladimir Prus
2008-11-13 13:42 ` Eli Zaretskii [this message]
2008-11-13 19:27 ` Vladimir Prus
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=u63msp8ie.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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