From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] new in next: thread joining and better quotes
Date: Thu, 24 Jan 2008 22:18:02 -0700 [thread overview]
Message-ID: <1201238225-sup-5297@tangerine.lanl.gov> (raw)
In-Reply-To: <1201237691-sup-3721@south>
Excerpts from William Morgan's message of Thu Jan 24 22:08:30 -0700 2008:
> Reformatted excerpts from William Morgan's message of 2008-01-16:
> > 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.
>
> Hm, this doesn't seem to always work...
>
I just tried and it worked. This is a really nice feature. I didn't
notice it before in the help menu and I've been wanting this feature.
prev parent reply other threads:[~2008-01-25 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 1:52 William Morgan
2008-01-25 5:08 ` William Morgan
2008-01-25 5:18 ` John Bent [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=1201238225-sup-5297@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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