From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@ges.redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa:doco] Reformat ``Remote Protocol'' appendix
Date: Wed, 14 Aug 2002 03:55:00 -0000 [thread overview]
Message-ID: <3405-Wed14Aug2002135202+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3D59A180.4090403@ges.redhat.com> (message from Andrew Cagney on Tue, 13 Aug 2002 20:17:04 -0400)
> Date: Tue, 13 Aug 2002 20:17:04 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
>
> > Finally, perhaps there should be an index entry for each
> > packet/command.
>
> Yes. That is something to do next. Exactly how should it be done
> though? Something like:
> @cindex packet, e
> @cindex e packet
> et.al..
The latter is sufficient, I think.
The important question when inventing index entries is "what phrase
would one expect this item to be indexed with?"
next prev parent reply other threads:[~2002-08-14 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 10:30 Andrew Cagney
2002-08-04 12:09 ` Daniel Jacobowitz
2002-08-13 3:34 ` Eli Zaretskii
2002-08-13 17:17 ` Andrew Cagney
2002-08-14 3:55 ` Eli Zaretskii [this message]
2002-08-14 8:43 ` Andrew Cagney
2002-08-15 9:46 ` Eli Zaretskii
2002-08-15 16:18 ` Andrew Cagney
2002-08-18 12:11 ` Eli Zaretskii
2002-08-19 15:09 ` Andrew Cagney
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=3405-Wed14Aug2002135202+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@ges.redhat.com \
--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