From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Killed threads reappearing in inbox
Date: Sat, 06 Nov 2010 14:29:48 +0100 [thread overview]
Message-ID: <1289050088-sup-8173@midna.zekjur.net> (raw)
In-Reply-To: <1288879799-sup-5465@chris-eee>
Hi Chris,
Excerpts from Chris Parsons's message of 2010-11-04 15:22:02 +0100:
> If another mail arrives in the same thread then it shows up in my
> inbox, including the "killed" tag (as attachment).
Can you try updating to the latest version, which includes the following patch?
http://rubyforge.org/pipermail/sup-devel/2010-October/000780.html
If the problem still happens, can you please forward me the message with which
you have that problem? (gzip it before to make sure it doesn’t get modified in
any way)
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-11-06 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 14:22 Chris Parsons
2010-11-06 13:29 ` Michael Stapelberg [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=1289050088-sup-8173@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--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