From: Chong Yidong <cyd@stupidchicken.com>
Cc: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: spam manual update for Gnus
Date: Wed, 08 Feb 2006 15:56:06 -0500 [thread overview]
Message-ID: <87acd1o9i1.fsf@stupidchicken.com> (raw)
In-Reply-To: <4noe1h8uvw.fsf@lifelogs.com> (Ted Zlatanov's message of "8 Feb 2006 15:20:51 -0500")
>> (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.
>
> 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?
If the Gnus CVS version of spam.el contains just bug fixes, I think it
should definitely be checked in. (For better or worse, RMS' criteria
for releasing Emacs is not based on a freeze, but on fixing bugs :-P)
next prev parent reply other threads:[~2006-02-08 20:56 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 [this message]
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=87acd1o9i1.fsf@stupidchicken.com \
--to=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).