From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] On making kill-thread easier
Date: Thu, 20 Aug 2009 16:36:15 -0400 [thread overview]
Message-ID: <1250800492-sup-136@Longbow> (raw)
In-Reply-To: <1250797598-sup-5105@tiger.alporthouse.com>
Excerpts from Chris Wilson's message of Thu Aug 20 16:01:10 -0400 2009:
> Hi everybody! I've just started using sup after Carl told me he'd found
> a fantastic new mail client. And, as usual, he was right.
If you're half as verbose as he is, I'll never have time to read it all!
;)
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
next prev parent reply other threads:[~2009-08-20 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 17:07 Carl Worth
2009-08-20 18:19 ` Andrei Thorp
2009-08-20 20:01 ` Chris Wilson
2009-08-20 20:36 ` Andrei Thorp [this message]
2009-08-20 21:07 ` Carl Worth
2009-08-20 20:43 ` Ben Walton
2009-08-20 21:11 ` Carl Worth
2009-08-20 22:56 ` Ben Walton
2009-08-21 0:09 ` Carl Worth
2009-08-21 1:36 ` Carl Worth
2009-08-21 15:16 ` Chris Wilson
2009-08-21 15:19 ` Edward Z. Yang
2009-08-21 15:20 ` Ben Walton
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=1250800492-sup-136@Longbow \
--to=garoth@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