From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] new in next: thread joining and better quotes
Date: Wed, 16 Jan 2008 17:52:57 -0800 [thread overview]
Message-ID: <1200533604-sup-2015@south> (raw)
Some minor quote-detection improvements in next, so tell me if the quote
blocks (the "+ (n quoted lines)" blocks) are wrong. I don't think I'll
be able to always get all cases, but at least the more common ones
should be detected now.
Also, you can now select multiple threads and press '#' to join them
into one thread. Once you write this back to index, there's no good way
to split them apart besides sup-syncing, so be careful.
--
William <wmorgan-sup at masanjin.net>
next reply other threads:[~2008-01-17 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 1:52 William Morgan [this message]
2008-01-25 5:08 ` William Morgan
2008-01-25 5:18 ` John Bent
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=1200533604-sup-2015@south \
--to=wmorgan-sup@masanjin.net \
/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