Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: kendall@clarkparsia.com (Kendall Grant Clark)
Subject: [sup-talk] Kill thread doesn't seem to work
Date: Wed, 19 Mar 2008 11:20:37 -0400	[thread overview]
Message-ID: <1205939956-sup-9857@k-desktop.int.clarkparsia.com> (raw)
In-Reply-To: <1205892920-sup-9762@south>

Excerpts from William Morgan's message of Tue Mar 18 22:16:02 -0400 2008:
> This should work. Can you try against git next? There have been a couple
> commits that probably affected this.

Doesn't work for me w/ git next either. I asked a coworker to send me
a message, I replied. Then I killed the thread. He replied to my
reply, and it popped right up in my INBOX with the +killed tag on it.

-- 
Cheers,
Kendall


  parent reply	other threads:[~2008-03-19 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 16:50 Kendall Grant Clark
2008-03-19  2:16 ` William Morgan
2008-03-19 13:59   ` Kendall Grant Clark
2008-03-19 14:51     ` John Bent
2008-03-19 15:17       ` Kendall Grant Clark
2008-03-19 16:20     ` William Morgan
2008-03-19 16:45       ` Kendall Grant Clark
2008-03-19 15:20   ` Kendall Grant Clark [this message]
2008-03-19 15:24     ` Giorgio Lando
2008-03-19 19:23       ` 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=1205939956-sup-9857@k-desktop.int.clarkparsia.com \
    --to=kendall@clarkparsia.com \
    /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