From: steve@patter.mine.nu (Stephen Patterson)
Subject: [sup-talk] split threads?
Date: Mon, 25 Aug 2008 23:09:34 +0100 [thread overview]
Message-ID: <20080825220933.GA27491@patter.mine.nu> (raw)
In-Reply-To: <1219624661-sup-6433@entry>
On 24 Aug 08, William Morgan (wmorgan-sup at masanjin.net) wrote:
> All the time! I'd love to have this. I'd also love to figure out why
> thread joining doesn't work, half the time.
For me (ok, I'm still using sup 0.5 because debian gem won't update to
0.6) thread joining works until you exit sup. i.e. the join-status
isn't saved back to the message index.
--
Stephen Patterson :: steve at patter.me.uk :: http://patter.mine.nu/
GPG: B416F0DE :: Jabber: patter at jabber.earth.li
"Don't be silly, Minnie. Who'd be walking round these cliffs with a gas oven?"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080825/9f27b9b4/attachment.bin>
next prev parent reply other threads:[~2008-08-25 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 22:23 Ben Walton
2008-08-25 0:38 ` William Morgan
2008-08-25 22:09 ` Stephen Patterson [this message]
2008-08-25 23:18 ` 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=20080825220933.GA27491@patter.mine.nu \
--to=steve@patter.mine.nu \
/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