From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: update 'target remote' description
Date: Thu, 09 Mar 2006 15:41:00 -0000 [thread overview]
Message-ID: <ufylss05v.fsf@gnu.org> (raw)
In-Reply-To: <vt2lkvlvqji.fsf@theseus.home.> (message from Jim Blandy on Tue, 07 Mar 2006 14:27:45 -0800)
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Tue, 07 Mar 2006 14:27:45 -0800
>
>
> src/gdb/doc/ChangeLog:
> 2006-03-07 Jim Blandy <jimb@red-bean.com>
>
> * gdb.texinfo (Target Commands): Update text describing how to
> specify a target. Refer to the detailed section on remote
> debugging, not the brief mention.
This is approved, but:
> +@item target remote @var{medium}
> +@cindex @code{target remote}
> @cindex remote target
Please remove this cindex entry. You already added such an entry
where the detailed description of this command is given; having
another one here is redundant, and even harmful, since this section
doesn't really explain about the command.
> +@code{target remote} supports the @code{load} command. This is only
> +useful if you have some other way of getting the stub to the target
> +system, and you can put it somewhere in memory where it won't get
> +clobbered by the download.
I'm guessing that this paragraph might be important in some situation
(which one, btw?), otherwise you wouldn't be adding it. So perhaps an
index entry related to that situation would in order here. What
phrases would a person who looks for this information have in mind?
Thanks.
next prev parent reply other threads:[~2006-03-09 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 10:57 Jim Blandy
2006-03-09 15:41 ` Eli Zaretskii [this message]
2006-03-09 19:11 ` Jim Blandy
2006-03-09 21:45 ` Eli Zaretskii
2006-03-10 0:29 ` Jim Blandy
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=ufylss05v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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