From: bdwalton@gmail.com (Ben Walton)
Subject: [sup-talk] split threads?
Date: Mon, 25 Aug 2008 19:18:10 -0400 [thread overview]
Message-ID: <f96e0240808251618y116ad5b6qf2c3141004858711@mail.gmail.com> (raw)
In-Reply-To: <20080825220933.GA27491@patter.mine.nu>
> 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.
Although I haven't tried joining threads since updating to 0.6, I
experienced the same behaviour you describe. It's not persistent, but
it always word well during a session.
-Ben
--
---------------------------------------------------------------------------------------------------------------------------
Ben Walton <bdwalton at gmail.com>
When one person suffers from a delusion, it is called insanity. When
many people suffer from a delusion it is called Religion.
Robert M. Pirsig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------------------------------------------------------------
prev parent reply other threads:[~2008-08-25 23:18 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
2008-08-25 23:18 ` Ben Walton [this message]
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=f96e0240808251618y116ad5b6qf2c3141004858711@mail.gmail.com \
--to=bdwalton@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