From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: acm@muc.de, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Feature freeze postphoned to end-July
Date: Wed, 11 Jun 2008 22:08:44 +0300 [thread overview]
Message-ID: <u1w33kcw3.fsf@gnu.org> (raw)
In-Reply-To: <87iqwgrmg9.fsf@stupidchicken.com>
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, acm@muc.de, emacs-devel@gnu.org
> Date: Wed, 11 Jun 2008 12:00:22 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Stefan Monnier <monnier@iro.umontreal.ca>
> >> Date: Tue, 10 Jun 2008 17:17:39 -0400
> >> Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
> >>
> >> Other than the Carbon changes, what would be the main reasons for
> >> a 22.3 release?
> >
> > A few bugfixes, i.e. a more stable 22.x release to fill the gap until
> > 23.1 is ready.
>
> I can't remember the last time a crash bug was reported/fixed in the
> branch.
??? Since when the only bugs we care about are crashes?
> I guess the thing to do is to go through the ChangeLogs and draw up a
> list of changes made to the branch since 22.2.
They are all supposed to be bugfixes.
next prev parent reply other threads:[~2008-06-11 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 16:03 Feature freeze postphoned to end-July Chong Yidong
2008-06-10 16:42 ` Alan Mackenzie
2008-06-10 20:28 ` Eli Zaretskii
2008-06-10 21:17 ` Stefan Monnier
2008-06-10 21:25 ` Eli Zaretskii
2008-06-11 16:00 ` Chong Yidong
2008-06-11 19:08 ` Eli Zaretskii [this message]
2008-06-11 21:33 ` Chong Yidong
2008-06-12 3:07 ` Eli Zaretskii
2008-06-11 19:27 ` Emacs 22 branch (was: Feature freeze postphoned to end-July) Reiner Steib
2008-06-10 18:21 ` Feature freeze postphoned to end-July Phil Hagelberg
2008-06-10 18:52 ` Stefan Monnier
2008-06-10 19:39 ` Chong Yidong
2008-06-11 19:48 ` Reiner Steib
2008-06-12 16:57 ` Chong Yidong
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=u1w33kcw3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).