From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
Project Archer <archer@sourceware.org>
Subject: Re: [python][patch] Preserve string length, and embedded-nulls in pretty-print string emission.
Date: Tue, 23 Jun 2009 16:56:00 -0000 [thread overview]
Message-ID: <4A41093D.7060806@redhat.com> (raw)
In-Reply-To: <m3skhqlxdk.fsf@fleche.redhat.com>
On 06/23/2009 05:37 PM, Tom Tromey wrote:
>>>>>> "Phil" == Phil Muldoon<pmuldoon@redhat.com> writes:
>>>>>>
>
> Phil> I've implemented requested changes. What do you think?
>
> Looks good!
>
Great! I'll check this in to the archer branch. I'll prepare and merge
this patch and the previous "counted string" patch for submission to GDB
soon after ...
> Phil> * python/lib/gdb/libstdcxx/v6/printers.py
>
> The rule I've been following for this stuff is that a libstdc++
> printer can't go in until the needed code is in gdb CVS.
> So, it is time to submit these last couple of changes upstream :-)
>
And then I'll submit these changes to libstdc++ later, post approval of
the previous GDB submit.
Regards
Phil
next prev parent reply other threads:[~2009-06-23 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 20:23 Phil Muldoon
2009-05-27 17:35 ` Tom Tromey
2009-05-27 18:24 ` Phil Muldoon
2009-05-27 20:22 ` Tom Tromey
2009-06-01 16:26 ` Phil Muldoon
2009-06-02 5:11 ` Thiago Jung Bauermann
2009-06-02 23:46 ` Tom Tromey
2009-06-08 10:31 ` Phil Muldoon
2009-06-11 17:12 ` Tom Tromey
2009-06-15 20:50 ` Phil Muldoon
2009-06-16 12:44 ` Phil Muldoon
2009-06-16 18:07 ` Tom Tromey
2009-06-18 12:20 ` Phil Muldoon
2009-06-18 20:17 ` Tom Tromey
2009-06-18 20:21 ` Tom Tromey
2009-06-23 14:37 ` Phil Muldoon
2009-06-23 16:37 ` Tom Tromey
2009-06-23 16:56 ` Phil Muldoon [this message]
2009-06-02 15:38 ` Jonas Maebe
2009-06-02 20:48 ` Phil Muldoon
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=4A41093D.7060806@redhat.com \
--to=pmuldoon@redhat.com \
--cc=archer@sourceware.org \
--cc=bauerman@br.ibm.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).