Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
		  Pedro Alves <pedro_alves@portugalmail.pt>
Subject: Re: [rfc] Shared libraries over the remote protocol, take two
Date: Mon, 18 Jun 2007 20:13:00 -0000	[thread overview]
Message-ID: <m3d4ztqawa.fsf@codesourcery.com> (raw)
In-Reply-To: <20070618150211.GA23415@caradoc.them.org> (Daniel Jacobowitz's message of "Mon, 18 Jun 2007 11:02:11 -0400")


Daniel Jacobowitz <drow@false.org> writes:
> Index: gdb/doc/gdb.texinfo
> ===================================================================
> --- gdb/doc/gdb.texinfo.orig	2007-06-18 10:15:05.000000000 -0400
> +++ gdb/doc/gdb.texinfo	2007-06-18 10:15:14.000000000 -0400
> @@ -12856,58 +12856,80 @@ If you do, that may be a bug in your rem
>  in @value{GDBN}.  You may want to report the problem to the
>  @value{GDBN} developers.
>  
> -The available settings are:
> +For each packet @var{name}, the command to enable or disable the
> +packet is @code{set remote @var{name}-packet}.  The available settings
> +are:

Not a big deal by any means, but: while I understand the appeal of not
repeating '-packet' over and over again, I wonder if this is going to
lead to questions as people jump straight to the table and skip the
explanation.  It seems to me there's some value in having the table
list exactly what you're supposed to type.


  parent reply	other threads:[~2007-06-18 20:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 15:02 Daniel Jacobowitz
2007-06-18 19:32 ` Jim Blandy
2007-06-18 19:38   ` Daniel Jacobowitz
2007-06-18 22:04     ` Jim Blandy
2007-06-18 22:20       ` Daniel Jacobowitz
2007-06-18 20:05 ` Eli Zaretskii
2007-07-02 19:03   ` Daniel Jacobowitz
2007-06-18 20:10 ` Jim Blandy
2007-06-18 20:13 ` Jim Blandy [this message]
2007-06-18 20:33   ` Daniel Jacobowitz
2007-06-18 22:06     ` Jim Blandy
2007-06-18 21:13 ` Pedro Alves
2007-07-02 22:01 ` 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=m3d4ztqawa.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    --cc=uweigand@de.ibm.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