From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfc/rfa:doco] Use @sc{gdb}?
Date: Fri, 23 Aug 2002 15:42:00 -0000 [thread overview]
Message-ID: <3D66B84F.6010803@ges.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
Hello,
(I'm really not sure about this one :-)
I got annoyed at all the GDB's in the formatted manual being really
large so tried changing them to @sc{gdb}. It fixed that problem but I'm
not sure that I like the final result :-) (You'll need to build
gdb.pdf, gdb ps or gdb.dvi).
Is there a style guide thing on this one? Eli?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1081 bytes --]
2002-08-23 Andrew Cagney <ac131313@redhat.com>
* all-cfg.texi: Use @sc for GDB and GCC. Update copyright.
Index: all-cfg.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/all-cfg.texi,v
retrieving revision 1.2
diff -u -r1.2 all-cfg.texi
--- all-cfg.texi 6 Mar 2001 08:21:41 -0000 1.2
+++ all-cfg.texi 23 Aug 2002 22:29:27 -0000
@@ -1,5 +1,6 @@
@c GDB MANUAL configuration file.
-@c Copyright 1993, 1995, 1999 Free Software Foundation, Inc.
+@c
+@c Copyright 1993, 1995, 1999, 2002 Free Software Foundation, Inc.
@c
@c NOTE: While the GDB manual is configurable (by changing these
@c switches), its configuration is ***NOT*** automatically tied in to
@@ -31,15 +32,14 @@
@set GDBP gdb
@c
@c Name of GDB product. Used in running text.
-@set GDBN GDB
+@set GDBN @sc{gdb}
@c
@c Name of host. Should not be used in generic configs, but generic
@c value may catch some flubs.
@set HOST machine specific
@c
@c Name of GCC product
-@set NGCC GCC
+@set NGCC @sc{gcc}
@c
@c Name of GCC program
@set GCC gcc
-
next reply other threads:[~2002-08-23 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 15:42 Andrew Cagney [this message]
2002-08-24 2:31 ` Eli Zaretskii
2002-09-26 10:40 ` Andrew Cagney
2002-09-26 12:05 ` Kevin Buettner
2002-09-26 12:52 ` Andrew Cagney
2002-09-27 9:40 ` Eli Zaretskii
2002-09-27 10:55 ` 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=3D66B84F.6010803@ges.redhat.com \
--to=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