From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [python] python-utils.c (python_string_to_unicode): Always return a new reference.
Date: Thu, 26 Feb 2009 18:41:00 -0000 [thread overview]
Message-ID: <m3r61lcc5a.fsf@fleche.redhat.com> (raw)
In-Reply-To: <49A654A6.8050504@redhat.com> (Phil Muldoon's message of "Thu\, 26 Feb 2009 08\:36\:54 +0000")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Phil> 2009-02-26 Phil Muldoon <pmuldoon@redhat.com>
Phil> * python/python-utils.c (python_string_to_unicode): Always
Phil> return
Phil> a new reference.
[...]
This is ok.
thanks,
Tom
prev parent reply other threads:[~2009-02-26 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 18:01 Phil Muldoon
2009-02-26 18:41 ` Tom Tromey [this message]
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=m3r61lcc5a.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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