public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: archer@sourceware.org
Subject: [python] [commit] Fix some duplicates in gdb.texinfo
Date: Fri, 07 Jan 2011 13:34:00 -0000	[thread overview]
Message-ID: <m31v4oalc8.fsf@redhat.com> (raw)


This just fixes some duplicates, and an spurious newline.

--

commit c9185e91a51fbb0fe2588cdd298a1854adcdf8aa
Author: Phil Muldoon <pmuldoon@redhat.com>
Date:   Fri Jan 7 13:31:34 2011 +0000

    Remove duplicate gdb.Breakpoints entry and spurious newline.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index c860c87..4442d74 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -20796,12 +20796,6 @@ Return a sequence holding all of @value{GDBN}'s breakpoints.
 @xref{Breakpoints In Python}, for more information.
 @end defun
 
-@findex gdb.breakpoints
-@defun breakpoints
-Return a sequence holding all of @value{GDBN}'s breakpoints.
-@xref{Breakpoints In Python}, for more information.
-@end defun
-
 @findex gdb.parameter
 @defun parameter parameter
 Return the value of a @value{GDBN} parameter.  @var{parameter} is a
@@ -20819,7 +20813,6 @@ type, and returned.
 @defun history number
 Return a value from @value{GDBN}'s value history (@pxref{Value
 History}).  @var{number} indicates which history element to return.
-
 If @var{number} is negative, then @value{GDBN} will take its absolute value
 and count backward from the last element (i.e., the most recent element) to
 find the value to return.  If @var{number} is zero, then @value{GDBN} will

                 reply	other threads:[~2011-01-07 13:34 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=m31v4oalc8.fsf@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).