From: Eric Sherman <hyperbolist@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] idle and unidle updates
Date: Thu, 14 Jan 2010 09:31:22 -0500 [thread overview]
Message-ID: <1263479269-sup-3220@changeling.local> (raw)
In-Reply-To: <1263478703-sup-3527@masanjin.net>
Excerpts from William Morgan's message of Thu Jan 14 09:22:45 -0500 2010:
> Are you going to send a second patch that makes use of these events to
> do the accumulation?
Yes. I wanted to wait till this was accepted though since I wasn't sure
about submitting a patch that depends on another patch.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-01-14 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:56 Eric Sherman
2010-01-14 14:22 ` William Morgan
2010-01-14 14:31 ` Eric Sherman [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=1263479269-sup-3220@changeling.local \
--to=hyperbolist@gmail.com \
--cc=sup-devel@rubyforge.org \
/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