From: Nick Roberts <nickrob@snap.net.nz>
Cc: Juanma Barranquero <lekktu@gmail.com>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: How about a new pretest?
Date: Tue, 19 Dec 2006 08:38:32 +1300 [thread overview]
Message-ID: <17798.60984.342170.380829@kahikatea.snap.net.nz> (raw)
In-Reply-To: <87wt4pccoo.fsf@stupidchicken.com>
Chong Yidong writes:
> "Juanma Barranquero" <lekktu@gmail.com> writes:
>
> > 2006/10/27 - 22.0.90
> > 2006/11/18 - 22.0.91
> > 2006/12/18 - waiting... :)
>
> It's been waiting on a few big issues, including the now-resolved
> C-mode slowness problem. The main sticking point now is the signal
> handling stuff that Kim started up about two weeks ago. I have no
> idea what's going on over there.
I think each pretest tarball should be a release candidate. So I can't see the
point of a new pretest while bugs are still listed in FOR-RELEASE, other than
to create the illusion that the release is getting nearer.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-12-18 19:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 17:02 How about a new pretest? Juanma Barranquero
2006-12-18 17:54 ` Chong Yidong
2006-12-18 19:38 ` Nick Roberts [this message]
2006-12-18 20:38 ` Eli Zaretskii
2006-12-19 0:46 ` Juanma Barranquero
2006-12-18 20:13 ` Eli Zaretskii
2006-12-19 10:13 ` Kim F. Storm
2006-12-19 15:41 ` Kim F. Storm
2006-12-19 20:30 ` Chong Yidong
2006-12-19 22:37 ` Lennart Borgman
2006-12-19 22:40 ` Juanma Barranquero
2006-12-20 15:04 ` David Kastrup
2006-12-20 15:23 ` Juanma Barranquero
2006-12-20 13:01 ` Richard Stallman
2006-12-21 10:47 ` Jason Rumney
2006-12-21 13:41 ` Kim F. Storm
2006-12-21 23:18 ` Richard Stallman
2006-12-22 0:34 ` Kim F. Storm
2006-12-22 21:52 ` Stefan Monnier
2006-12-23 20:13 ` Richard Stallman
2006-12-25 13:30 ` Kim F. Storm
2006-12-23 20:13 ` Richard Stallman
2006-12-23 20:42 ` Lennart Borgman
2006-12-24 17:09 ` Richard Stallman
2006-12-24 17:22 ` Lennart Borgman
2006-12-21 23:18 ` Richard Stallman
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=17798.60984.342170.380829@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.