Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Move remote stuff to new chapter
Date: Mon, 21 Jan 2002 10:56:00 -0000	[thread overview]
Message-ID: <3C4C646C.2070403@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020121122406.17248B-100000@is>

> On Mon, 21 Jan 2002, Andrew Cagney wrote:
> 
> 
>> With that in mind, I'd like to propose that a new chapter be created: 
>> ``Debugging remote programs''.  The attatched patch is a first cut at this.
>> 
>> The second thing to consider (not done here) is to remove the remote 
>> protocol specification to an appendix.  It is very much like the 
>> maintenance commands.  While they are one of GDB's interfaces they are 
>> pretty obscure and not part of normal reading.
>> 
>> Thoughts?
> 
> 
> I think it's a good change.


Thanks.  I've checked the first change in.  Standby for another patch.

Andrew




      reply	other threads:[~2002-01-21 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20 22:48 Andrew Cagney
2002-01-21  2:25 ` Eli Zaretskii
2002-01-21 10:56   ` Andrew Cagney [this message]

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=3C4C646C.2070403@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.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