From: Tom Tromey <tromey@redhat.com>
To: Oguz Kayral <oguzkayral@gmail.com>
Cc: archer@sourceware.org
Subject: Re: [RFC][3/5] Stop event subclasses
Date: Mon, 21 Sep 2009 21:56:00 -0000 [thread overview]
Message-ID: <m3ab0ox8q4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <36a35d480908230836x6c8f4eaap142f85744484318b@mail.gmail.com> (Oguz Kayral's message of "Sun, 23 Aug 2009 18:36:12 +0300")
>>>>> "Oguz" == Oguz Kayral <oguzkayral@gmail.com> writes:
Oguz> These three new files contain subclasses to event class adding more
Oguz> functionality for stop events.
[...]
... continuing the previous message, if we just used a dictionary to
represent an event, that would eliminate a lot of C code -- this entire
patch.
Tom
prev parent reply other threads:[~2009-09-21 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 15:36 Oguz Kayral
2009-09-21 21:56 ` 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=m3ab0ox8q4.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).