Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: ding@gnus.org
Subject: Re: spam manual update for Gnus
Date: Mon, 06 Feb 2006 23:49:15 +0100	[thread overview]
Message-ID: <v9oe1k14t0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nirrsgrfc.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "6 Feb 2006 15:31:35 -0500")

On Mon, Feb 06 2006, Ted Zlatanov wrote:

> I see the problem, I am using the Ding CVS, and you are using the
> Emacs CVS.

Ted, if you don't want to check out Emacs CVS, you can use the v5-10
branch in Gnus' CVS.

> What's the right approach here?  I would guess we should make the
> changes in both places, but start with Ding.  Do you agree?  

The spam.el (and spam-report.el) code differs between the Gnus CVS
trunk and the v5-10 branch (which is synced to/from Emacs CVS).  I
think that in the v5-10 branch there is some inconsistency between
code and documentation, see
<http://thread.gmane.org/gmane.emacs.gnus.general/60921>.  I didn't
have time to dig into it, though.  (I already mentioned this in a
previous mail to Chong)

(I didn't look at the patch yet.  But...)  I'd guess that we should
start from v5-10/Emacs CVS and update to the new code in the trunk
later.  Assuming that the next Emacs release is more close than the
next stable Gnus release.

> Is anyone willing to help me and Chong proofread?

I'd like to; but I can't promise when.  But I only have practical
experience with the (quite unusual) setup described in (info
"(gnus)Spam ELisp Package Configuration Examples").

It would be good if some "ordinary users" (the less you know about the
internals, the better. ;-)) could help proofreading.

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



  reply	other threads:[~2006-02-06 22:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 20:59 Gnus manual update Chong Yidong
2006-02-06 19:18 ` Ted Zlatanov
2006-02-06 20:19   ` Chong Yidong
2006-02-06 20:31     ` spam manual update for Gnus (was: Gnus manual update) Ted Zlatanov
2006-02-06 22:49       ` Reiner Steib [this message]
2006-02-08 20:20         ` spam manual update for Gnus Ted Zlatanov
2006-02-08 20:56           ` Chong Yidong
2006-02-09 15:00           ` spam.el: Bugs, compatibility with v5-10 (was: spam manual update for Gnus) Reiner Steib
2006-02-13 19:04             ` spam.el: Bugs, compatibility with v5-10 Ted Zlatanov
2006-02-13 22:36               ` Emacs 20.7 compatibility in v5-10 (was: spam.el: Bugs, compatibility with v5-10) Reiner Steib
2006-03-20 19:51                 ` Emacs 20.7 compatibility in v5-10 Ted Zlatanov
2006-03-20 20:38                   ` Reiner Steib
2006-02-13 19:15             ` ham destination bugs (was: spam.el: Bugs, compatibility with v5-10) Ted Zlatanov
2006-02-14 15:04               ` ham destination bugs Reiner Steib
2006-02-20 14:29                 ` Reiner Steib
2006-05-27 10:17                   ` Reiner Steib
2006-05-30 13:55                     ` Ted Zlatanov
2006-06-08 20:54                   ` spam.el spam-summary-prepare-exit rewrite (was: ham destination bugs) Ted Zlatanov
2006-04-19 14:23           ` spam manual update for Gnus Reiner Steib
2006-04-20 18:18             ` Ted Zlatanov
2006-04-20 18:38               ` Chong Yidong
2006-04-20 20:08               ` Reiner Steib
2006-04-20 23:20                 ` Miles Bader
2006-04-20 18:45             ` Ted Zlatanov
2006-02-06 20:25   ` message mode screwy (was: Gnus manual update) Ted Zlatanov
2006-02-08 16:52     ` message mode screwy Reiner Steib
2006-02-09 15:37       ` Ted Zlatanov
2006-02-13 18:58         ` Ted Zlatanov
2006-02-13 22:15           ` Adam Sjøgren
2006-02-13 22:39           ` Reiner Steib

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=v9oe1k14t0.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).