From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sent mail in inbox view
Date: Mon, 21 Dec 2009 11:31:21 -0800 [thread overview]
Message-ID: <1261423846-sup-2484@masanjin.net> (raw)
In-Reply-To: <1261421239-sup-6142@tangerine.lanl.gov>
Reformatted excerpts from John Bent's message of 2009-12-21:
> Ferret still. Scared to change. One day... This adds motivation.
I'm still using Ferret too. Weird that it would work for me and not for
you.
Poll time: is joining threads NOT persistent for anyone else?
--
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-21 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 14:19 C. Morgan Hamill
2009-12-19 19:14 ` William Morgan
2009-12-19 21:27 ` Helge Titlestad
2009-12-19 22:26 ` Ben Walton
2009-12-20 1:22 ` Cameron Matheson
2009-12-21 16:56 ` John Bent
2009-12-21 18:13 ` William Morgan
2009-12-21 18:25 ` John Bent
2009-12-21 18:34 ` William Morgan
2009-12-21 18:47 ` John Bent
2009-12-21 19:31 ` William Morgan [this message]
2009-12-21 20:02 ` Tarko Tikan
2009-12-20 2:17 ` Tero Tilus
2009-12-21 13:45 ` William Morgan
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=1261423846-sup-2484@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