From: Steven Walter <stevenrwalter@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] "Force tags to be joined" doesn't save
Date: Mon, 2 Nov 2009 11:47:51 -0500 [thread overview]
Message-ID: <e06498070911020847v6e91024am4af1d4901dee7ef6@mail.gmail.com> (raw)
If I select two threads and combine them with #, sup seems to combine
them, and the current view becomes "modified." If I save ($) and
reload (@), the threads show up separately again. Is this expected
behavior?
--
-Steven Walter <stevenrwalter@gmail.com>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-11-02 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 16:47 Steven Walter [this message]
2009-11-02 19:22 ` William Morgan
2009-11-02 19:32 ` 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=e06498070911020847v6e91024am4af1d4901dee7ef6@mail.gmail.com \
--to=stevenrwalter@gmail.com \
--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