Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: spam-stat warning
Date: Tue, 28 Jun 2011 09:25:16 -0500	[thread overview]
Message-ID: <87k4c6nicz.fsf@lifelogs.com> (raw)
In-Reply-To: <m3r57a7ekp.fsf@quimbies.gnus.org>

On Sat, 04 Jun 2011 00:08:54 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I don't think many people are using spam-stat.el anyway, so changing
>> this immediately is OK with me.  Do you want:
>> 
>> (defun spam-stat-install ()
>> (interactive)
>> (when spam-stat-install-hooks
>> (spam-stat-install-hooks-function)))
>> 
>> or were you thinking deeper surgery?

LMI> I think that would be fine.

I see you made that change; thank you.

Ted




      reply	other threads:[~2011-06-28 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 21:09 Lars Magne Ingebrigtsen
2011-06-01 13:09 ` Ted Zlatanov
2011-06-03 22:08   ` Lars Magne Ingebrigtsen
2011-06-28 14:25     ` Ted Zlatanov [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=87k4c6nicz.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).