From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] before-add-message hook no creating threads
Date: Sun, 14 Mar 2010 10:54:28 +0200 [thread overview]
Message-ID: <1268556523-sup-2164@tilus.net> (raw)
In-Reply-To: <79968.51859.qm@web63906.mail.re1.yahoo.com>
Daren Lord, 2010-03-11 17:47:
> I am trying to take certain emails and lump them into a thread so I
> can keep track of the history
Why not use labels? That is exactly what labels are for. Isn't it?
> Here is the code from my before-add-message.rb hook:
>
> if message.subj =~ /^\[ENV (PROD|TEST|DEV)\] Hourly ADDM report for instance (.*)/
> message.add_ref $1 + "ADDM REPORTS - " + $2
Sup expects ref to be a message id. In principle that should work,
but the expectation could bite you here. Have you tried using id from
an existing message?
> message.add_label "report"
> message.add_label $1
> end
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-03-14 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 15:47 Daren Lord
2010-03-14 8:54 ` Tero Tilus [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=1268556523-sup-2164@tilus.net \
--to=tero@tilus.net \
--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