From: Tom Tromey <tromey@redhat.com>
To: sam shepperd <samshepperd@gmail.com>
Cc: archer@sourceware.org, oguzkayral@gmail.com
Subject: Re: Python event handling status?
Date: Wed, 11 Nov 2009 23:11:00 -0000 [thread overview]
Message-ID: <m38wec64j9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <9a0bd7f70911091948q2f643b85j9505fc257e726de0@mail.gmail.com> (sam shepperd's message of "Mon, 9 Nov 2009 21:48:57 -0600")
>>>>> "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
next prev parent reply other threads:[~2009-11-11 23:11 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 [this message]
2009-11-12 8:28 ` Oguz Kayral
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=m38wec64j9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=oguzkayral@gmail.com \
--cc=samshepperd@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).