From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] matchreply (deliver mails into folders with associated threads)
Date: Mon, 24 Oct 2005 12:51:52 +0900 [thread overview]
Message-ID: <435C5A58.5060404@gmail.com> (raw)
In-Reply-To: <434C1F23.7020702@gmail.com>
Tejun Heo wrote:
>
> Hello, all.
>
> This isn't really linux kernel related but I wrote this to track LKML
> discussion threads better and I hope this can make following LKML a
> little bit easier for others too.
>
> What matchreply does is to enable procmail to deliver a message into
> the folder containing its associated thread. So, when you find an
> interesting thread on LKML, just move the thread into your 'interested'
> folder, and then all follow-up messages will be delievered there.
>
> matchreply assumes Maildir format folders and uses inotify, so you need
> kernel version >= 2.6.13.
>
> README (explains how to setup .procmailrc) is at
>
> http://home-tj.org/matchreply/files/README
>
> Source tarball
>
> http://home-tj.org/matchreply/files/matchreply-0.1.tar.gz
>
> Binaries for i386 and x86_64
>
> http://home-tj.org/matchreply/files/binary-matchreply-0.1-i386
> http://home-tj.org/matchreply/files/binary-matchreply-0.1-x86_64
>
> Thanks.
>
A bugfix release 0.11 is available. A buffer overflow bug in
log_message() is fixed. What can be overwritten by overflowing the
buffer is only "\n\0", so it shouldn't be very dangerous. Still, it's a
buffer overflow which can be triggered by incoming messages. Please
update. Sorry for the hassle.
http://home-tj.org/wiki/index.php/Matchreply
http://home-tj.org/files/matchreply/matchreply-0.11.tar.gz
http://home-tj.org/files/matchreply/binary-matchreply-0.11-x86_64
http://home-tj.org/files/matchreply/binary-matchreply-0.11-i386
Thanks.
--
tejun
prev parent reply other threads:[~2005-10-24 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 20:22 [ANNOUNCE] matchreply (deliver mails into folders with associated threads) Tejun Heo
2005-10-24 3:51 ` Tejun Heo [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=435C5A58.5060404@gmail.com \
--to=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.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