From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] sup-sync-back: killed threads and read status
Date: Mon, 15 Oct 2007 01:42:23 -0500 [thread overview]
Message-ID: <1192430420-sup-9514@chris-tablet> (raw)
In-Reply-To: <6205b42d0710142302u2ca4c6c0yc53336434bc4fe39@mail.gmail.com>
Excerpts from Pierre Baillet's message of Mon Oct 15 01:02:12 -0500 2007:
> sup-sync-back does not seem to delete killed messages. I think, it should do
> that.
That make sense to be. "Kill thread" (&) is more like "Ignore thread"
than "Delete thread" (d) (at least to me). I still want it in my index
in case I want to get something from it later. I am, however, no longer
interested in it or changes to it.
--
Christopher Warrington <chrisw at rice.edu>
next prev parent reply other threads:[~2007-10-15 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 6:02 Pierre Baillet
2007-10-15 6:42 ` Christopher Warrington [this message]
2007-10-29 15:46 ` 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=1192430420-sup-9514@chris-tablet \
--to=chrisw@rice.edu \
/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