Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Release of Gnus 5.10.10 / No Gnus 0.8
Date: Wed, 09 Apr 2008 21:15:38 +0200	[thread overview]
Message-ID: <v98wzmon51.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mskxvjsmx.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 09 Apr 2008 18:15:50 +0900")

On Wed, Apr 09 2008, Katsumi Yamaoka wrote:

>>>>>> Reiner Steib wrote:
>> On Tue, Mar 25 2008, Reiner Steib wrote:
>>> *Code freeze*
>>>
>>> I think we should have a couple of days *without any code changes* on
>>> the v5-10 branch (*doc fixes* are okay) and only include important bug
>>> fixes[2] or doc fixes on the trunk.
>
> Both Gnus 5.10.10 and No Gnus 0.8 don't work with the most recent
> Emacs trunk.  

It doesn't make any sense to run the _released_ No Gnus 0.8 with Emacs
trunk.  Somebody who is willing to use (i.e. *test*) bleeding edge
code of Emacs has to be prepared live with such breakage, go back to
an older checkout or update again as soon as the bugs have been fixed.

For the combination Emacs trunk plus Gnus 5.10.10, the only reasonable
use-case would be that Gnus 5.13 is much more unstable that the rest
of Emacs trunk.  I don't think this is true.

Or does someone see other reasonable scenarios?

In short: If you use Emacs trunk, you should use either the bundled
Gnus 5.13 or Gnus trunk (when newer).

> http://article.gmane.org/gmane.emacs.devel/94760

,----[ <news:b4m7if7pilg.fsf@jpl.org> ]
| 1. Merge Stefan's changes:
| 
| 2008-04-07  Stefan Monnier  <monnier@iro.umontreal.ca>
| 
| 	* mail-source.el (mail-source-value):
| 	Prefer fboundp to functionp so it works with macros as well.
| 
| 2008-04-03  Stefan Monnier  <monnier@iro.umontreal.ca>
| 
| 	* gnus-win.el (gnus-configure-frame, gnus-all-windows-visible-p):
| 	Fix last change in case the element is not even a symbol.
| 
| 2008-03-20  Stefan Monnier  <monnier@iro.umontreal.ca>
| 
| 	* gnus-win.el (gnus-configure-frame, gnus-all-windows-visible-p):
| 	Prefer fboundp to functionp so it works with macros as well.
| 
|    I'm not sure that's all, though.
`----

I hesitate to merge in these before the release as they might
introduce other problems.

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



  reply	other threads:[~2008-04-09 19:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 18:34 Reiner Steib
2008-03-25 18:50 ` Chris Uzdavinis
2008-03-25 19:05   ` Adam Sjøgren
2008-03-25 19:24 ` Zlatko Calusic
2008-03-25 20:30   ` Adam Sjøgren
2008-03-25 22:02     ` Zlatko Calusic
2008-03-25 22:13 ` Katsumi Yamaoka
2008-03-25 23:43   ` Reiner Steib
2008-03-26  8:24     ` Didier Verna
2008-03-26  9:34       ` Katsumi Yamaoka
2008-03-26 21:11       ` Reiner Steib
2008-03-28 14:24       ` Ted Zlatanov
2008-03-28 14:44 ` Ted Zlatanov
2008-04-09  7:27 ` Reiner Steib
2008-04-09  8:09   ` Gabor Z. Papp
2008-04-09 18:44     ` Reiner Steib
2008-04-09  9:15   ` Katsumi Yamaoka
2008-04-09 19:15     ` Reiner Steib [this message]
2008-04-09 22:53       ` Katsumi Yamaoka
2008-04-10 10:44         ` Reiner Steib
2008-04-10 17:51   ` Reiner Steib
2008-04-10 18:49     ` Ted Zlatanov
2008-04-10 19:05       ` Reiner Steib
2008-04-11  6:43     ` 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=v98wzmon51.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).