From: "Richard M. Stallman" <rms@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: bootstrap problem with union Lisp_Object
Date: Wed, 14 Dec 2005 00:12:07 -0500 [thread overview]
Message-ID: <E1EmOvv-0006hX-Oz@fencepost.gnu.org> (raw)
In-Reply-To: <jwvwti97zan.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 13 Dec 2005 11:12:22 -0500)
I'm not working hard on fixing bugs, indeed, because I pretty demotivated by
the never ending "preparation for pretest" and because those non-trivial
bugs don't have nearly enough info: we need more testers.
That would be a good point, if not for the fact that we seem to have a
person who can give us useful feedback now. Yidong is working
effectively on that particular bug. Meanwhile, there are all the others
which are not nearly so hard, but do take work.
next prev parent reply other threads:[~2005-12-14 5:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 17:32 bootstrap problem with union Lisp_Object Ken Raeburn
2005-12-06 7:50 ` Ken Raeburn
2005-12-06 11:44 ` Andreas Schwab
2005-12-06 15:44 ` Stefan Monnier
2005-12-06 15:52 ` Andreas Schwab
2005-12-06 16:20 ` Stefan Monnier
2005-12-06 16:30 ` Andreas Schwab
2005-12-07 20:12 ` Ken Raeburn
2005-12-08 4:54 ` Richard M. Stallman
2005-12-08 8:59 ` Ken Raeburn
2005-12-09 1:41 ` Richard M. Stallman
2005-12-09 4:36 ` Stefan Monnier
2005-12-09 5:06 ` Henrik Enberg
2005-12-09 5:16 ` Luc Teirlinck
2005-12-09 9:54 ` Juri Linkov
2005-12-10 4:14 ` Richard M. Stallman
2005-12-09 21:14 ` Richard M. Stallman
2005-12-09 21:14 ` Richard M. Stallman
2005-12-09 21:54 ` Chong Yidong
2005-12-10 9:15 ` Eli Zaretskii
2005-12-11 5:02 ` Richard M. Stallman
2005-12-11 14:43 ` Chong Yidong
2005-12-11 22:57 ` Richard M. Stallman
2005-12-12 5:11 ` Chong Yidong
2005-12-13 3:14 ` Richard M. Stallman
2005-12-11 22:57 ` Richard M. Stallman
2005-12-12 5:18 ` Chong Yidong
2005-12-13 3:14 ` Richard M. Stallman
2005-12-13 3:53 ` Chong Yidong
2005-12-13 23:33 ` Richard M. Stallman
2005-12-14 0:12 ` Chong Yidong
2005-12-13 16:12 ` Stefan Monnier
2005-12-14 5:12 ` Richard M. Stallman [this message]
2005-12-14 14:13 ` Chong Yidong
2005-12-15 2:09 ` Richard M. Stallman
2005-12-15 3:40 ` Stefan Monnier
2005-12-16 1:51 ` Richard M. Stallman
2005-12-16 10:35 ` Kim F. Storm
2005-12-17 1:04 ` Richard M. Stallman
2005-12-17 3:46 ` Chong Yidong
2005-12-17 23:59 ` Richard M. Stallman
2005-12-17 5:46 ` Chong Yidong
2005-12-14 9:24 ` Kim F. Storm
2005-12-10 23:28 ` Kim F. Storm
2005-12-11 4:56 ` Pretest? [was: Re: bootstrap problem with union Lisp_Object] Nick Roberts
2005-12-11 16:49 ` bootstrap problem with union Lisp_Object Richard M. Stallman
2005-12-07 20:04 ` Ken Raeburn
2005-12-06 21:05 ` Benjamin Riefenstahl
2005-12-07 17:06 ` Richard M. Stallman
2005-12-06 21:55 ` Richard M. Stallman
2005-12-06 22:26 ` Stefan Monnier
2005-12-06 16:41 ` Richard M. 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=E1EmOvv-0006hX-Oz@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.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.
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).