Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: "Ted Zlatanov" <tzz@lifelogs.com>,
	"Chong Yidong" <cyd@stupidchicken.com>
Subject: Re: spam manual update for Gnus
Date: Wed, 19 Apr 2006 16:23:44 +0200	[thread overview]
Message-ID: <v9vet5hcen.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4noe1h8uvw.fsf@lifelogs.com> (Ted Zlatanov's message of "8 Feb 2006 15:20:51 -0500")

On Wed, Feb 08 2006, Ted Zlatanov wrote:

> The differences are pretty major, and I would actually like to bring
> the CVS version of spam.el and spam-report.el over to Emacs CVS.
> There's a lot of bug fixes, but no new features and no bug reports
> with the CVS version of spam.el/spam-report.el for a while now.  Is
> this possible?

We dropped support for Emacs 20.7 and XEmacs 21.1 in v5-10 as well (as
we've done in the trunk when starting No Gnus).  So technically it
should be possible to sync spam*.el to v5-10.  But given that Emacs
seems to enter pretest soon and(as previously mentioned in this
thread[1]) there are some unfixed bugs in the trunk version that are
not present in v5-10, I'd suggest not to do this now.

> That being said, Chong's version of the manual looks good after a
> first read.  I will probably suggest minor changes here and there, but
> I am really glad he wrote something better than my original version :)

However, as Chong's improvements to the manual are made for
Emacs/v5-10, I think we should install those in Emacs/v5-10 now.  I
don't know if Ted has already made his "minor changes" based on
Chong's patch.  If not, I'd suggest that Chong installs his changes in
Emacs' CVS now.

Bye, Reiner.

[1] <news:v964nakssy.fsf@marauder.physik.uni-ulm.de>
    http://thread.gmane.org/gmane.emacs.gnus.general/61845/focus=61991
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2006-04-19 14:23 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       ` spam manual update for Gnus Reiner Steib
2006-02-08 20:20         ` 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           ` Reiner Steib [this message]
2006-04-20 18:18             ` spam manual update for Gnus 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=v9vet5hcen.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=cyd@stupidchicken.com \
    --cc=tzz@lifelogs.com \
    /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).