From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [RFA] add note on command naming to gdbint.texi
Date: Thu, 03 Jun 2010 18:14:00 -0000 [thread overview]
Message-ID: <20100603181353.E965584396@ruffy.mtv.corp.google.com> (raw)
Hi.
I'd like to add this to the Coding section of gdbint.texi.
Ok?
2010-06-03 Doug Evans <dje@google.com>
* gdbint.texinfo (Coding): Add subsection on command names.
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.323
diff -u -p -r1.323 gdbint.texinfo
--- doc/gdbint.texinfo 2 May 2010 23:52:14 -0000 1.323
+++ doc/gdbint.texinfo 3 Jun 2010 18:05:31 -0000
@@ -6245,6 +6245,10 @@ the code detected a user error, recovere
@code{warning} or the code failed to correctly recover from the user
error and issued an @code{internal_error}.}
+@subsection Command Names
+
+GDB U/I commands are written @samp{foo-bar}, not @samp{foo_bar}.
+
@subsection File Names
Any file used when building the core of @value{GDBN} must be in lower
next reply other threads:[~2010-06-03 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 18:14 Doug Evans [this message]
2010-06-03 18:44 ` Eli Zaretskii
2010-06-03 19:36 ` Tom Tromey
2010-06-03 20:31 ` Stan Shebs
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=20100603181353.E965584396@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.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