From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch][doc] PR python/10781
Date: Tue, 27 Oct 2009 20:58:00 -0000 [thread overview]
Message-ID: <4AE75ED0.8080503@redhat.com> (raw)
In-Reply-To: <833a54fzks.fsf@gnu.org>
On 10/27/2009 06:42 PM, Eli Zaretskii wrote:
>> Date: Tue, 27 Oct 2009 15:52:03 +0000
>> From: Phil Muldoon<pmuldoon@redhat.com>
>> CC: Tom Tromey<tromey@redhat.com>, gdb-patches@sourceware.org
>>
>> On 10/16/2009 08:08 PM, Eli Zaretskii wrote:
>>
>>> Here's the text that I propose to use:
>>>
>>> +@defmethod Value cast type
>>> +Return a new instance of @code{gdb.Value} that is the result of
>>> +casting this instance to the type described by @var{type},
>>> +which must be a @code{gdb.Type} object. If the cast cannot be
>>> +performed for some reason, this method throws an exception.
>>> +@end defmethod
>>>
>>>
>> Ok to check this patch in?
>>
> If you are asking me, the answer is obviously yes,
Ok, thanks. Checked in.
> since it's text I
> wrote.
>
I was being deferential. The patch was based on text that was already
written, and rewritten by another at a later date. I as purely being
the facilitator to fix a bug reported by a user. I encouraged that user
to file the bug, and I decided to make sure the various patches were
filed. I decided it was best to check in this case.
Cheers!
Phil
next prev parent reply other threads:[~2009-10-27 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 7:35 Phil Muldoon
2009-10-16 7:46 ` Eli Zaretskii
2009-10-16 18:07 ` Tom Tromey
2009-10-16 18:44 ` Eli Zaretskii
2009-10-16 18:49 ` Tom Tromey
2009-10-16 19:09 ` Eli Zaretskii
2009-10-19 17:50 ` Tom Tromey
2009-10-27 15:52 ` Phil Muldoon
2009-10-27 16:01 ` Phil Muldoon
2009-10-27 18:43 ` Eli Zaretskii
2009-10-27 20:58 ` Phil Muldoon [this message]
2009-10-27 21:14 ` Eli Zaretskii
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=4AE75ED0.8080503@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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