From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] BSD libkvm documentation
Date: Fri, 09 Jul 2004 18:52:00 -0000 [thread overview]
Message-ID: <6654-Fri09Jul2004215158+0300-eliz@gnu.org> (raw)
In-Reply-To: <200407040703.i64734Di071430@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Sun, 4 Jul 2004 09:03:04 +0200 (CEST))
> Date: Sun, 4 Jul 2004 09:03:04 +0200 (CEST)
> From: Mark Kettenis <kettenis@chello.nl>
>
> Also it seems that current practice is to give every command a
> @kindex entry.
I've now fixed all such entries[1] so that if there are a few commands
with a common prefix, say "foo bar", then only "@kindex foo bar" is in
the index. Where appropriate, I added @cindex entries to help find
the relevant info via index search.
Let me know if some of the changes I made need more work.
Footnotes:
[1] Well, almost all such entries: there are borderline cases such as
for the command `set', `show', `info', `maint', etc., that are
scattered through the entire manual, and it is neither practical nor
IMHO desirable to remove them.
prev parent reply other threads:[~2004-07-09 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 13:32 Mark Kettenis
2004-07-03 21:09 ` Eli Zaretskii
2004-07-04 7:03 ` Mark Kettenis
2004-07-04 19:14 ` Eli Zaretskii
2004-07-05 16:04 ` Mark Kettenis
2004-07-09 18:52 ` Eli Zaretskii [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=6654-Fri09Jul2004215158+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--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