Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org, "Gnus" <ding@gnus.org>
Subject: Re: Removing spam-group-ham-mark-p, spam-group-spam-mark-p
Date: 3 Feb 2006 14:39:01 -0500	[thread overview]
Message-ID: <4nu0bgw7u2.fsf@lifelogs.com> (raw)
In-Reply-To: <v9ek3ixsrm.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 08 Jan 2006 23:24:29 +0100")

On  8 Jan 2006, reinersteib+gmane@imap.cc wrote:

> Chong Yidong on emacs-diffs:
>
>> --- emacs/lisp/gnus/ChangeLog:1.414	Sat Dec 17 21:41:33 2005
>> +++ emacs/lisp/gnus/ChangeLog	Sun Jan  8 21:29:46 2006
>>>> -1,3 +1,10 @@
>> +2006-01-08  Chong Yidong  <cyd@stupidchicken.com>
>> +
>> +	* spam.el (spam-group-ham-mark-p, spam-group-spam-mark-p)
>> +	(spam-group-spam-marks): Delete functions.
>> +	(spam-list-articles): Just call spam-group-ham-marks directly.
>> +	(spam-group-ham-marks): Simplify.
>
> I'd appreciate if you would discuss non-trivial changes to Gnus on the
> Gnus developer list before committing.

Chong, was there a reason for deleting them?  Are they slow?  I'd like
to keep them too.

Ted

p.s. sorry for the late reply, I just caught up with ding :)



  reply	other threads:[~2006-02-03 19:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Evi6k-000363-G0@savannah.gnu.org>
2006-01-08 22:24 ` Removing spam-group-ham-mark-p, spam-group-spam-mark-p (was: Changes to emacs/lisp/gnus/ChangeLog) Reiner Steib
2006-02-03 19:39   ` Ted Zlatanov [this message]
2006-02-04 23:09     ` Removing spam-group-ham-mark-p, spam-group-spam-mark-p Reiner Steib
2006-02-06 18:54       ` Ted Zlatanov

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=4nu0bgw7u2.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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).