From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Karl Berry <karl@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: @dircategory for gdb manuals
Date: Tue, 25 May 2004 21:27:00 -0000 [thread overview]
Message-ID: <40B3BA23.2090407@gnu.org> (raw)
In-Reply-To: <200404101902.i3AJ2UD13760@tug.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3101 bytes --]
Eli, are the attatched tweaks ok, for 6.1.1?
Andrew
--- Begin Message  ---
From : karl at gnu dot org (Karl Berry)
To : gdb at sources dot redhat dot com
Date : Sat, 10 Apr 2004 21:02:30 +0200
Subject : @dircategory for gdb manuals
Delivery-date : Sat, 10 Apr 2004 15:02:55 -0400
Envelope-to : cagney@gnu.org
(Sorry if this is the wrong place, mail to bug-gdb only elicited a
suggestion to try here.)
I'd like to suggest the following minor changes to the GDB manuals to
change their categories in the Texinfo dir file -- I've been trying to
rationalize these categories per rms's suggestions. (I know that
"Software libraries" is not exactly right for internals documents, but
it is the closest we've got.)
Also, the frontmatter should be changed to use @copying, the GNU free
documentation license, @ifnottex around the Top node, etc. -- this patch
doesn't do those things. See
http://texinfo.org/manual/Document-Permissions.html
http://texinfo.org/manual/GNU-Sample-Texts.html
for information and for an example of recommended frontmatter for GNU
manuals. Right now, the copying information doesn't end up in the HTML
output, for instance, which is not a good thing.
Finally, at one point there seems to have been a libgdb.texinfo. Is
that no longer being distributed? I don't see it in the 6.0
distribution. (I'd just like to remove it from my example dir file, if
it's truly gone.)
Please let me know if questions or problems.
Thanks,
karl (Texinfo maintainer)
*** ./ORIG/gdb.texinfo Sat Aug 9 08:10:35 2003
--- ./gdb.texinfo Sat Nov 15 09:03:32 2003
***************
*** 39,45 ****
@c This is a dir.info fragment to support semi-automated addition of
@c manuals to an info tree.
! @dircategory Programming & development tools.
@direntry
! * Gdb: (gdb). The @sc{gnu} debugger.
@end direntry
--- 39,45 ----
@c This is a dir.info fragment to support semi-automated addition of
@c manuals to an info tree.
! @dircategory Software development
@direntry
! * Gdb: (gdb). The GNU debugger.
@end direntry
*** ./ORIG/gdbint.texinfo Mon Aug 18 13:12:32 2003
--- ./gdbint.texinfo Sat Nov 15 09:05:42 2003
***************
*** 2,6 ****
@setfilename gdbint.info
@include gdb-cfg.texi
! @dircategory Programming & development tools.
@direntry
* Gdb-Internals: (gdbint). The GNU debugger's internals.
--- 2,6 ----
@setfilename gdbint.info
@include gdb-cfg.texi
! @dircategory Software libraries
@direntry
* Gdb-Internals: (gdbint). The GNU debugger's internals.
*** ./ORIG/stabs.texinfo Mon Aug 4 13:43:36 2003
--- ./stabs.texinfo Sat Nov 15 09:05:57 2003
***************
*** 4,14 ****
@c @finalout
! @ifinfo
! @format
! START-INFO-DIR-ENTRY
* Stabs: (stabs). The "stabs" debugging information format.
! END-INFO-DIR-ENTRY
! @end format
! @end ifinfo
@ifinfo
--- 4,11 ----
@c @finalout
! @dircategory Software libraries
! @direntry
* Stabs: (stabs). The "stabs" debugging information format.
! @end direntry
@ifinfo
--- End Message  ---
next parent reply other threads:[~2004-05-25 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200404101902.i3AJ2UD13760@tug.org>
2004-05-25 21:27 ` Andrew Cagney [this message]
2004-05-26 10:02 ` Eli Zaretskii
[not found] <200405261326.i4QDQTd11571@f7.net>
2004-05-27 7:15 ` Eli Zaretskii
[not found] <200405271341.i4RDfa025333@f7.net>
2004-05-28 8:30 ` Eli Zaretskii
[not found] <200405281324.i4SDOeS10812@f7.net>
2004-05-29 11:16 ` Eli Zaretskii
2004-05-31 19:21 ` Andrew Cagney
2004-06-01 4:24 ` Eli Zaretskii
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=40B3BA23.2090407@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=karl@gnu.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