From: Chong Yidong <cyd@stupidchicken.com>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: Build failure under Suse 10.0
Date: Tue, 31 Oct 2006 18:06:15 -0500 [thread overview]
Message-ID: <87lkmwqe54.fsf@stupidchicken.com> (raw)
In-Reply-To: <u7iyg6sj4.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 01 Nov 2006 00\:15\:43 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 31 Oct 2006 10:29:52 +0100
>> From: "Juanma Barranquero" <lekktu@gmail.com>
>> Cc: emacs-devel@gnu.org
>>
>> And, after all, we've been years waiting for the pretest. I don't
>> think a few days will make much difference.
>
> FWIW, I don't see any reasons to hurry with another pretest. AFAIR,
> we didn't yet hear from enough pretesters to have a clear idea of how
> many bugs are there, especially on unusual platforms.
For one thing, Richard hasn't sent out his announcement to the
emacs-pretesters list. I suggested to him to hold off making the
announcement: since 22.0.90 contains some obvious bugs that prevent
compilation on Windows, Mac, and OpenBSD, I think it's better to put
out a 22.0.91 tarball fixing this problems, so that testers won't
waste time reporting trivial "Emacs can't compile" bugs that are fixed
in CVS.
Do you disagree?
next prev parent reply other threads:[~2006-10-31 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 9:53 Build failure under Suse 10.0 Frank Schmitt
2006-10-30 23:16 ` Chong Yidong
2006-10-30 23:24 ` Frank Schmitt
2006-10-30 23:49 ` Nick Roberts
2006-10-31 0:26 ` Chong Yidong
2006-10-31 4:25 ` Eli Zaretskii
2006-10-31 15:25 ` Chong Yidong
2006-11-04 13:20 ` Eli Zaretskii
2006-10-31 9:29 ` Juanma Barranquero
2006-10-31 22:15 ` Eli Zaretskii
2006-10-31 23:06 ` Chong Yidong [this message]
2006-11-01 4:17 ` Eli Zaretskii
2006-11-02 4:42 ` 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
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=87lkmwqe54.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--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 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).