From: fjbender@googlemail.com (Florian Bender)
Subject: [sup-talk] Increase poll frequency
Date: Thu, 11 Dec 2008 21:30:39 +0100 [thread overview]
Message-ID: <1229027326-sup-7107@vicodin> (raw)
In-Reply-To: <1229026741-sup-2943@entry>
Excerpts from William Morgan's message of Do Dez 11 21:20:08 +0100 2008:
> There's no way to do this now, but it would be pretty easy to add.
Due to the fact that I'm no Ruby coder, I'd be glad if you could add it to the next release :-)
--
Florian Bender <fjbender at googlemail.com>
GPG Fingerprint: D0BB BDF9 5889 BC30 49F4 681D 84F7 6AC7 7C39 85F8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20081211/cd78f994/attachment.bin>
next prev parent reply other threads:[~2008-12-11 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 20:59 Florian Bender
2008-12-08 21:29 ` Ben Walton
[not found] ` <8F89701D-3DC1-4BAF-8A42-090D532FBF64@gmail.com>
2008-12-09 6:14 ` Florian Bender
2008-12-11 20:20 ` William Morgan
2008-12-11 20:30 ` Florian Bender [this message]
2008-12-11 20:41 ` Marc Hartstein
2008-12-12 1:37 ` William Morgan
2008-12-12 1:58 ` Christopher Warrington
2008-12-20 1:03 ` Marc Hartstein
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=1229027326-sup-7107@vicodin \
--to=fjbender@googlemail.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