Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] "maint set remote"
Date: Fri, 27 Oct 2006 09:15:00 -0000	[thread overview]
Message-ID: <uvem6t8z6.fsf@gnu.org> (raw)
In-Reply-To: <20061026212639.GA21608@nevyn.them.org> (message from Daniel 	Jacobowitz on Thu, 26 Oct 2006 17:26:39 -0400)

> Date: Thu, 26 Oct 2006 17:26:39 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> Per my discussion with Eli earlier today.  This patch removes most of
> the documentation for the individual packet commands, moves them under
> "maint", and aggregates their documentation into a table there.  The
> new bits of interest:

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?


  parent reply	other threads:[~2006-10-27  9:15 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 [this message]
2006-10-27 14:50   ` Daniel Jacobowitz
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=uvem6t8z6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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