public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: jkratoch@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer: Merge commit 'origin/archer-jankratochvil-python' into archer
Date: Mon, 09 Mar 2009 17:05:00 -0000	[thread overview]
Message-ID: <20090309170459.27959.qmail@sourceware.org> (raw)

The branch, archer has been updated
       via  ec29855686f2a78d90ebcc63765681249bbbe808 (commit)
       via  534f5de0c9569a9eae535d722864afa1d78dc9dc (commit)
       via  0874c29c3341c169ebaaf3f125792d57595fc525 (commit)
      from  543fb2154d3bd551344b990b911be5c6cc703504 (commit)

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

- Log -----------------------------------------------------------------
commit ec29855686f2a78d90ebcc63765681249bbbe808
Merge: 543fb2154d3bd551344b990b911be5c6cc703504 534f5de0c9569a9eae535d722864afa1d78dc9dc
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Mon Mar 9 18:03:07 2009 +0100

    Merge commit 'origin/archer-jankratochvil-python' into archer

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

Summary of changes:
 gdb/python/lib/gdb/libstdcxx/v6/printers.py |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

First 500 lines of diff:
diff --git a/gdb/python/lib/gdb/libstdcxx/v6/printers.py b/gdb/python/lib/gdb/libstdcxx/v6/printers.py
index ccef97d..c0dc987 100644
--- a/gdb/python/lib/gdb/libstdcxx/v6/printers.py
+++ b/gdb/python/lib/gdb/libstdcxx/v6/printers.py
@@ -615,6 +615,7 @@ def build_libstdcxx_dictionary ():
     pretty_printers_dict[re.compile('^std::stack<.*>$')] = lambda val: StdStackOrQueuePrinter("std::stack", val)
     pretty_printers_dict[re.compile('^std::unique_ptr<.*>$')] = UniquePointerPrinter
     pretty_printers_dict[re.compile('^std::vector<.*>$')] = StdVectorPrinter
+    # vector<bool>
 
     # These are the C++0x printers. They also exist in the standard namespace.
     # For array - the default GDB pretty-printer seems reasonable.
@@ -626,7 +627,7 @@ def build_libstdcxx_dictionary ():
     pretty_printers_dict[re.compile('^std::(tr1::)?unordered_multiset<.*>$')] = lambda val: Tr1UnorderedSetPrinter ('std::tr1::unordered_multiset', val)
 
 
-    # Extensions to std, tr1 pretty-printers.
+    # Extensions.
     pretty_printers_dict[re.compile('^__gnu_cxx::slist<.*>$')] = StdSlistPrinter
 
     if True:


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


             reply	other threads:[~2009-03-09 17:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 17:05 jkratoch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-30 19:06 jkratoch
2009-03-29 22:42 jkratoch
2009-03-27  0:35 jkratoch
2009-03-25 19:00 jkratoch
2009-03-24 17:33 jkratoch
2009-03-12 20:25 jkratoch
2009-03-06 21:16 jkratoch
2009-03-06 16:59 jkratoch
2009-03-06 14:26 jkratoch
2009-03-05 21:53 jkratoch
2009-03-05 21:15 jkratoch
2009-03-04 23:54 jkratoch
2009-03-04 22:34 jkratoch
2009-03-04 15:04 jkratoch
2009-03-03 21:47 jkratoch
2009-03-03 21:45 jkratoch
2009-03-02 22:55 jkratoch
2009-03-01 14:38 jkratoch
2009-02-28 19:26 jkratoch
2009-02-26 23:02 jkratoch

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=20090309170459.27959.qmail@sourceware.org \
    --to=jkratoch@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).