From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] Delete remaining obsolete files
Date: Fri, 13 Apr 2007 09:45:00 -0000 [thread overview]
Message-ID: <uhcrkk3pq.fsf@gnu.org> (raw)
In-Reply-To: <20070410202607.GA1046@caradoc.them.org> (message from Daniel Jacobowitz on Tue, 10 Apr 2007 16:26:07 -0400)
> Date: Tue, 10 Apr 2007 16:26:07 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> Of special interest is the shuffling of the Remote and Remote
> Debugging sections in the manual. I discovered that some places
> referred to a small summary of remote debugging in the Targets
> chapter, and other places referred to the beefier Remote Debugging
> chapter. Conveniently that chapter needed an introduction, so I moved
> the introduction from the section to the start of the chapter.
The changes in the manual are okay with me, but:
> -Once you've connected to the remote target, @value{GDBN} allows you to
> -send arbitrary commands to the remote monitor:
> -
> -@table @code
> -@item remote @var{command}
> -@kindex remote@r{, a command}
> -@cindex send command to remote monitor
> -Send an arbitrary @var{command} string to the remote monitor.
> -@end table
Why was this part removed?
> -@item set remotedevice @var{device}
> -@cindex serial port name
> -Set the name of the serial port through which to communicate to the
> -remote target to @var{device}. This is the device used by
> -@value{GDBN} to open the serial communications line to the remote
> -target. There's no default, so you must set a valid port name for the
> -remote serial communications to work. (Some varieties of the
> -@code{target} command accept the port name as part of their
> -arguments.)
> -
> -@item show remotedevice
> -Show the current name of the serial port.
Same here.
> Index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.220
> diff -u -p -r1.220 NEWS
This is fine, thanks.
next prev parent reply other threads:[~2007-04-13 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 20:26 Daniel Jacobowitz
2007-04-13 9:45 ` Eli Zaretskii [this message]
2007-04-13 11:21 ` 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=uhcrkk3pq.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