public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-tromey-python: add missing word to docs
Date: Fri, 04 Sep 2009 17:28:00 -0000	[thread overview]
Message-ID: <20090904172829.26185.qmail@sourceware.org> (raw)

The branch, archer-tromey-python has been updated
       via  7557187109afaf1d815cd6b1f54635924ff36809 (commit)
      from  bebf39ab4d5763fb1b25d73d858c68f8c75f04eb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 7557187109afaf1d815cd6b1f54635924ff36809
Author: Tom Tromey <tromey@redhat.com>
Date:   Fri Sep 4 11:28:22 2009 -0600

    add missing word to docs

-----------------------------------------------------------------------

Summary of changes:
 gdb/doc/gdb.texinfo |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

First 500 lines of diff:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 0e92ac7..374d113 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -23823,7 +23823,7 @@ begin with a @samp{*}), or one of the following:
 @samp{$@var{regname}} --- a CPU register name
 @end itemize
 
-A varobj's may be provided by a Python-based pretty-printer.  In this
+A varobj's contents may be provided by a Python-based pretty-printer.  In this
 case the varobj is known as a @dfn{dynamic varobj}.  Dynamic varobjs
 have slightly different semantics in some cases.  If the
 @code{-enable-pretty-printing} command is not sent, then @value{GDBN}


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2009-09-04 17:28 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=20090904172829.26185.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=archer-commits@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).