From: Andrew Cagney <cagney@gnu.org>
To: eliz@gnu.org
Cc: Karl Berry <karl@freefriends.org>, gdb-patches@sources.redhat.com
Subject: [6.1;rfa:doco] texinfo tweaks; Was: @dircategory for gdb manuals
Date: Mon, 14 Jun 2004 14:32:00 -0000 [thread overview]
Message-ID: <40CDB6E3.8070007@gnu.org> (raw)
In-Reply-To: <200406011304.i51D4tD01378@f7.net>
[-- Attachment #1: Type: text/plain, Size: 26 bytes --]
Eli, how is this?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2706 bytes --]
Index: doc/ChangeLog
2004-06-14 Andrew Cagney <cagney@gnu.org>
Based on changes from Karl Berry.
* gdb.texinfo: Do not use @sc in a direntry.
* stabs.texinfo: Change @dircateogry to "Software development".
* gdbint.texinfo, gdb.texinfo, annotate.texinfo: Ditto.
Index: doc/annotate.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/annotate.texinfo,v
retrieving revision 1.4
diff -p -u -r1.4 annotate.texinfo
--- doc/annotate.texinfo 24 Feb 2004 15:41:29 -0000 1.4
+++ doc/annotate.texinfo 14 Jun 2004 14:29:59 -0000
@@ -4,7 +4,7 @@
@c This is a dir.info fragment to support semi-automated addition of
@c manuals to an info tree.
-@dircategory Programming & development tools.
+@dircategory Software development
@direntry
* Annotate: (annotate). The obsolete annotation interface.
@end direntry
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.205
diff -p -u -r1.205 gdb.texinfo
--- doc/gdb.texinfo 10 Jun 2004 20:05:44 -0000 1.205
+++ doc/gdb.texinfo 14 Jun 2004 14:30:04 -0000
@@ -38,9 +38,9 @@
@c This is a dir.info fragment to support semi-automated addition of
@c manuals to an info tree.
-@dircategory Programming & development tools.
+@dircategory Software development
@direntry
-* Gdb: (gdb). The @sc{gnu} debugger.
+* Gdb: (gdb). The GNU debugger.
@end direntry
@ifinfo
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.208
diff -p -u -r1.208 gdbint.texinfo
--- doc/gdbint.texinfo 13 Jun 2004 13:42:33 -0000 1.208
+++ doc/gdbint.texinfo 14 Jun 2004 14:30:04 -0000
@@ -1,7 +1,7 @@
\input texinfo @c -*- texinfo -*-
@setfilename gdbint.info
@include gdb-cfg.texi
-@dircategory Programming & development tools.
+@dircategory Software development
@direntry
* Gdb-Internals: (gdbint). The GNU debugger's internals.
@end direntry
Index: doc/stabs.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/stabs.texinfo,v
retrieving revision 1.14
diff -p -u -r1.14 stabs.texinfo
--- doc/stabs.texinfo 24 Feb 2004 15:41:29 -0000 1.14
+++ doc/stabs.texinfo 14 Jun 2004 14:30:05 -0000
@@ -5,7 +5,7 @@
@c This is a dir.info fragment to support semi-automated addition of
@c manuals to an info tree.
-@dircategory Programming & development tools.
+@dircategory Software development
@direntry
* Stabs: (stabs). The "stabs" debugging information format.
@end direntry
next parent reply other threads:[~2004-06-14 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200406011304.i51D4tD01378@f7.net>
2004-06-14 14:32 ` Andrew Cagney [this message]
2004-06-14 18:52 ` Eli Zaretskii
2004-06-14 22:26 ` 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=40CDB6E3.8070007@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=karl@freefriends.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