From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Add an after-add-message hook
Date: Wed, 02 Sep 2009 06:53:17 -0700 [thread overview]
Message-ID: <1251899447-sup-1658@masanjin.net> (raw)
In-Reply-To: <1251153881-sup-1538@masanjin.net>
Reformatted excerpts from William Morgan's message of 2009-08-24:
> Branch after-add-message-hook, merged into next. Thanks!
I've had to unmerge this, because keeping all the messages around led to
memory problems with large mailboxes.
What about just using the before-add hook and either backgrounding the
process (if it's a separate process) or doing the processing in a Thread
(if it's Ruby code)?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-02 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 21:47 Kevin Riggle
2009-08-18 17:56 ` William Morgan
2009-08-18 23:36 ` Kevin Riggle
2009-08-19 18:55 ` William Morgan
2009-08-21 1:57 ` Kevin Riggle
2009-08-24 22:44 ` William Morgan
2009-09-02 13:53 ` William Morgan [this message]
2009-08-21 2:07 ` Kevin Riggle
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=1251899447-sup-1658@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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