unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Gnus for next release
Date: Mon, 10 May 2004 12:04:10 +0200	[thread overview]
Message-ID: <v93c688up1.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: x5wu3kn0nl.fsf@lola.goethe.zz

On Mon, May 10 2004, David Kastrup wrote:

> Miles Bader <miles@gnu.org> writes:
>
>> 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.
> [...]
>> So what about it?  Sounds pretty good and safe to me (and Gnus is
>> largely a standalone part of emacs).
>
> High time.  It should have been put in at least half a year ago.

In fact we started discussing it in January (see the thread
http://thread.gmane.org/gmane.emacs.gnus.general/55650).  (The
discussion started on the Gnus list.  Later it was Cc-ed to
emacs-devel, too.)

> While it missed the semi-official feature freeze, this was IMO just
> an oversight (didn't think of it myself): it is not that any mad
> rushes of last-minute fixes were what was causing this.

One reason for the Gnus developers' hesitation/delay might have been
the crypto problems which are solved now:
<URL:http://thread.gmane.org/E1BL6CW-0003Ge-8y@fencepost.gnu.org>.
Another reason for the delay were the bootstrap problems I encountered
starting to use Miles arch repositories
(<URL:http://thread.gmane.org/gmane.emacs.devel/21913>; Miles
suggested that merging using arch should be easier.)

I hope that we can merge Gnus 5.10 into the Emacs trunk despite of
being at little bit late.

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

  reply	other threads:[~2004-05-10 10:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09 23:07 Gnus for next release Miles Bader
2004-05-09 23:19 ` 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 [this message]
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=v93c688up1.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).