From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] unread status
Date: Tue, 29 Dec 2009 15:54:54 -0800 [thread overview]
Message-ID: <1262130868-sup-2032@masanjin.net> (raw)
In-Reply-To: <1262130179-sup-8306@zyrg.net>
Reformatted excerpts from Rich Lane's message of 2009-12-29:
> I should dust it off and resubmit. It will cause a UI-responsiveness
> regression for ferret users, but if ferret is going to be deprecated
> in the next release then I don't care too much.
Please do. Encouraging Ferret users to switch is fine. :)
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-29 23:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 14:47 Philipp Überbacher
2009-12-29 22:53 ` William Morgan
2009-12-29 23:12 ` Philipp Überbacher
2009-12-29 23:24 ` Tero Tilus
2009-12-29 23:49 ` Rich Lane
2009-12-29 23:54 ` William Morgan [this message]
2009-12-30 0:32 ` John Bent
2010-01-03 22:22 ` William Morgan
2010-03-05 15:59 ` John Bent
2010-03-05 20:00 ` John Bent
2010-03-05 20:32 ` John Bent
2009-12-29 23:33 ` William Morgan
2009-12-29 23:54 ` Philipp Überbacher
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 13:45 Philipp Überbacher
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=1262130868-sup-2032@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@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