From: "Michael Snyder" <msnyder@redhat.com>
To: <gdb-patches@sources.redhat.com>
Subject: [commit] spelling fix, gdb.texinfo
Date: Mon, 17 Jan 2005 21:21:00 -0000 [thread overview]
Message-ID: <007201c4fcda$88ad10d0$cba66b80@msnyder8600> (raw)
2005-01-17 Michael Snyder <msnyder@redhat.com>
* gdb.texinfo: Fix spelling, infinte -> infinite.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.229
diff -p -r1.229 gdb.texinfo
*** gdb.texinfo 8 Dec 2004 05:28:31 -0000 1.229
--- gdb.texinfo 17 Jan 2005 19:52:17 -0000
*************** that command. Post-execution hooks may
*** 14088,14094 ****
pre-execution hooks, for the same command.
It is valid for a hook to call the command which it hooks. If this
! occurs, the hook is not re-executed, thereby avoiding infinte recursion.
@c It would be nice if hookpost could be passed a parameter indicating
@c if the command it hooks executed properly or not. FIXME!
--- 14088,14094 ----
pre-execution hooks, for the same command.
It is valid for a hook to call the command which it hooks. If this
! occurs, the hook is not re-executed, thereby avoiding infinite recursion.
@c It would be nice if hookpost could be passed a parameter indicating
@c if the command it hooks executed properly or not. FIXME!
reply other threads:[~2005-01-17 21:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='007201c4fcda$88ad10d0$cba66b80@msnyder8600' \
--to=msnyder@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