From: Tom Tromey <tromey@redhat.com>
To: Oguz Kayral <oguzkayral@gmail.com>
Cc: archer@sourceware.org
Subject: Re: [RFC][0/5] Python event handling
Date: Mon, 21 Sep 2009 21:17:00 -0000 [thread overview]
Message-ID: <m33a6gyp4d.fsf@fleche.redhat.com> (raw)
In-Reply-To: <36a35d480908230834y46a44e08od4645db444bb5e7a@mail.gmail.com> (Oguz Kayral's message of "Sun, 23 Aug 2009 18:34:25 +0300")
>>>>> "Oguz" == Oguz Kayral <oguzkayral@gmail.com> writes:
Oguz> This patch series adds inferior event handling support to GDB Python
Oguz> scripting. The work is based on archer-tromey-python branch.
Hi Oguz.
I'm sorry about the long delay in my response here. I spent most of
August on another part of the Python interface and didn't have much time
left over.
I have a few comments on the patches. I will reply to the patches
needing comment.
One bigger thing, not specific to any particular patch, is that we like
to have documentation for all new Python APIs.
Tom
next prev parent reply other threads:[~2009-09-21 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 15:34 Oguz Kayral
2009-09-21 21:17 ` Tom Tromey [this message]
2009-09-24 1:52 ` Richard Ward
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=m33a6gyp4d.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=oguzkayral@gmail.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).