From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] "maint set remote"
Date: Fri, 27 Oct 2006 14:50:00 -0000 [thread overview]
Message-ID: <20061027145036.GA19544@nevyn.them.org> (raw)
In-Reply-To: <uvem6t8z6.fsf@gnu.org>
On Fri, Oct 27, 2006 at 11:15:57AM +0200, Eli Zaretskii wrote:
> Thanks, but you've removed all the text that explained what GDB
> features rely on each packet. For example, the documentation of
> verbose-resume-packet mentioned that it affects debugging of
> multithreaded programs.
>
> How about adding another column to the @multitable to include that
> information where appropriate?
Shouldn't that be in the documentation for the packet (where it
generally already is)? If you still think it should be by the
commands, I can add a column with brief pointers.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-27 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 21:26 Daniel Jacobowitz
2006-10-27 7:44 ` Jim Blandy
2006-10-27 14:52 ` Daniel Jacobowitz
2006-10-27 9:15 ` Eli Zaretskii
2006-10-27 14:50 ` Daniel Jacobowitz [this message]
2006-10-27 21:59 ` Daniel Jacobowitz
2006-10-28 11:01 ` Eli Zaretskii
2006-11-14 16:02 ` Daniel Jacobowitz
2006-11-14 20:48 ` Eli Zaretskii
2006-11-14 21:40 ` 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=20061027145036.GA19544@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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