From: Oguz Kayral <oguzkayral@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: sam shepperd <samshepperd@gmail.com>, archer@sourceware.org
Subject: Re: Python event handling status?
Date: Thu, 12 Nov 2009 08:28:00 -0000 [thread overview]
Message-ID: <36a35d480911120028h7967cf40h502170ecd22d2a24@mail.gmail.com> (raw)
In-Reply-To: <m38wec64j9.fsf@fleche.redhat.com>
Unfortunately, life has been keeping me extremely busy for the last
few months. I've had no time to spend on the reviews. But you can
expect some updates in the next weeks.
2009/11/12 Tom Tromey <tromey@redhat.com>:
>>>>>> "sam" == sam shepperd <samshepperd@gmail.com> writes:
>
> sam> Is there any update on the status of python event handling? Having
> sam> this ability would be very powerful and useful. It does not seem to
> sam> be in git even though the patches were submitted back in August:
> sam> http://sourceware.org/ml/archer/2009-q3/msg00148.html
>
> I sent some review comments a bit later.
> Basically this patch series needs someone to hack on them and champion
> them a bit.
>
> Tom
>
prev parent reply other threads:[~2009-11-12 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 3:49 sam shepperd
2009-11-11 23:11 ` Tom Tromey
2009-11-12 8:28 ` Oguz Kayral [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=36a35d480911120028h7967cf40h502170ecd22d2a24@mail.gmail.com \
--to=oguzkayral@gmail.com \
--cc=archer@sourceware.org \
--cc=samshepperd@gmail.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).