From: Miles Bader <miles@gnu.org>
Subject: Gnus for next release
Date: Sun, 9 May 2004 19:07:20 -0400 [thread overview]
Message-ID: <20040509230720.GB20485@fencepost> (raw)
I've been talking with the Gnus developers, and it comes up that it would
probably be a good idea to put the current stable release of Gnus into the
next Emacs release.
Here's what one Gnus maintainer says (just to clarify the version numbering,
Gnus 5.10.x is the branch being suggested for inclusion, but it would be
renamed 5.11 when added to the Emacs tree):
Reiner Steib <reiner.steib@gmx.de> wrote:
> It's even more than one year since the release of Gnus 5.10.1
> (2003-05-01). After that, only bugfixes went into 5.10.[1-6]. Since
> the release of 5.10.6 (2004-01-04) there was only single commit to the
> v5-10 branch. (Some post-5.10.6 doc-fixes could be merged from the
> trunk to v5-10).
>
> I also expect that merging Gnus v5-10 into the Emacs trunk won't lead
> to significant problems (or even to a delay of Emacs release).
> Looking at the "User-Agent" headers, you'll notice that many people
> already use Gnus v5.10.6 (or No Gnus) with Emacs 21.3.50.
>
> It would be a pity if Gnus 5.11 would not be included in the next
> Emacs release because it has many improvements over 5.9.
So what about it? Sounds pretty good and safe to me (and Gnus is largely a
standalone part of emacs).
-Miles
--
=====
(^o^;
(()))
*This is the cute octopus virus, please copy it into your sig so it can spread.
next reply other threads:[~2004-05-09 23:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 23:07 Miles Bader [this message]
2004-05-09 23:19 ` Gnus for next release John Wiegley
2004-05-09 23:29 ` Stefan Monnier
2004-05-09 23:54 ` Miles Bader
2004-05-10 7:34 ` Frank Schmitt
2004-05-10 8:31 ` David Kastrup
2004-05-10 10:04 ` Reiner Steib
2004-05-11 12:22 ` Possible problem with Gnus Richard Stallman
2004-05-11 12:40 ` David Kastrup
2004-05-12 19:40 ` Richard Stallman
2004-05-11 13:48 ` Stefan Monnier
2004-05-11 16:07 ` Reiner Steib
2004-05-11 16:31 ` Paul Jarc
2004-05-12 9:59 ` Reiner Steib
2004-05-12 14:15 ` Paul Jarc
2004-05-12 15:48 ` Jesper Harder
2004-05-12 16:39 ` Reiner Steib
2004-05-12 15:36 ` Jesper Harder
2004-05-11 17:51 ` Stefan Monnier
2004-05-12 9:59 ` Reiner Steib
2004-05-12 10:34 ` David Kastrup
2004-05-13 15:45 ` Richard Stallman
2004-05-13 17:25 ` David Kastrup
2004-05-13 17:59 ` Stefan Monnier
2004-05-13 19:07 ` David Kastrup
2004-05-14 21:01 ` Richard Stallman
2004-05-14 21:18 ` David Kastrup
2004-05-15 18:33 ` Richard Stallman
2004-05-23 3:46 ` Andy Tai
2004-05-23 3:48 ` Andy Tai
2004-05-10 17:54 ` Gnus for next release Richard Stallman
2004-05-10 18:23 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040509230720.GB20485@fencepost \
--to=miles@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).