From: Elena Zannoni <ezannoni@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/DOCO] annotate.texinfo
Date: Tue, 11 Nov 2003 14:09:00 -0000 [thread overview]
Message-ID: <16304.60827.237938.78186@localhost.redhat.com> (raw)
In-Reply-To: <uznf3qvvt.fsf@elta.co.il>
Eli Zaretskii writes:
> > From: Elena Zannoni <ezannoni@redhat.com>
> > Date: Mon, 10 Nov 2003 17:54:15 -0500
> >
> > +@c This is a dir.info fragment to support semi-automated addition of
> > +@c manuals to an info tree.
> > +@dircategory Programming & development tools.
> > +@direntry
> > +* Annotate: (gdb). The obsolete annotation interface.
> > +@end direntry
>
> Okay, but shouldn't we have "(annotate)." rather than "(gdb)." here?
>
> Does the link from info/dir work? I'd expect it to get you to the
> wrong manual.
doh. Indeed you are right. "info annotate" would show the gdb info manual.
fixed and committed:
2003-11-11 Elena Zannoni <ezannoni@redhat.com>
* stabs.texinfo: Add dircategory and direntry commands.
* annotate.texinfo: Ditto.
Index: annotate.texinfo
===================================================================
RCS file: /cvs/uberbaum/gdb/doc/annotate.texinfo,v
retrieving revision 1.2
diff -u -p -r1.2 annotate.texinfo
--- annotate.texinfo 24 Oct 2003 17:37:04 -0000 1.2
+++ annotate.texinfo 11 Nov 2003 14:07:28 -0000
@@ -1,6 +1,14 @@
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename annotate.info
+
+@c This is a dir.info fragment to support semi-automated addition of
+@c manuals to an info tree.
+@dircategory Programming & development tools.
+@direntry
+* Annotate: (annotate). The obsolete annotation interface.
+@end direntry
+
@c
@include gdb-cfg.texi
@c
Index: stabs.texinfo
===================================================================
RCS file: /cvs/uberbaum/gdb/doc/stabs.texinfo,v
retrieving revision 1.11
diff -u -p -r1.11 stabs.texinfo
--- stabs.texinfo 4 Aug 2003 20:43:57 -0000 1.11
+++ stabs.texinfo 11 Nov 2003 14:07:33 -0000
@@ -3,13 +3,12 @@
@c @finalout
-@ifinfo
-@format
-START-INFO-DIR-ENTRY
-* Stabs: (stabs). The "stabs" debugging information format.
-END-INFO-DIR-ENTRY
-@end format
-@end ifinfo
+@c This is a dir.info fragment to support semi-automated addition of
+@c manuals to an info tree.
+@dircategory Programming & development tools.
+@direntry
+* Stabs: (stabs). The "stabs" debugging information format.
+@end direntry
@ifinfo
This document describes the stabs debugging symbol tables.
prev parent reply other threads:[~2003-11-11 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 0:25 Elena Zannoni
2003-11-08 17:10 ` Eli Zaretskii
2003-11-10 22:54 ` Elena Zannoni
2003-11-11 6:07 ` Eli Zaretskii
2003-11-11 14:09 ` Elena Zannoni [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=16304.60827.237938.78186@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=eliz@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