Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Gnus <ding@gnus.org>, emacs-devel@gnu.org
Subject: Removing spam-group-ham-mark-p, spam-group-spam-mark-p (was: Changes to emacs/lisp/gnus/ChangeLog)
Date: Sun, 08 Jan 2006 23:24:29 +0100	[thread overview]
Message-ID: <v9ek3ixsrm.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1Evi6k-000363-G0@savannah.gnu.org>

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.

I intend to add functionality[1] in the current development version of
Gnus that relies on the functions `spam-group-ham-mark-p' and
`spam-group-spam-mark-p'.

[1] Adding a tool bar button for `gnus-summary-mark-as-spam' depending
    on the result of `spam-group-ham-mark-p', along with improving the
    tool bar in general.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

       reply	other threads:[~2006-01-08 22:24 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 ` Reiner Steib [this message]
2006-02-03 19:39   ` Removing spam-group-ham-mark-p, spam-group-spam-mark-p Ted Zlatanov
2006-02-04 23:09     ` 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=v9ek3ixsrm.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).