From: Chong Yidong <cyd@stupidchicken.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Starting pretest
Date: Fri, 06 Oct 2006 22:01:32 -0400 [thread overview]
Message-ID: <8764ewsx37.fsf@stupidchicken.com> (raw)
In-Reply-To: <85wt7cyldu.fsf@lola.goethe.zz> (David Kastrup's message of "Sat\, 07 Oct 2006 03\:17\:49 +0200")
David Kastrup <dak@gnu.org> writes:
> Richard Stallman <rms@gnu.org> writes:
>
>> October 1.
>>
>> Even if he replies during the pretest, we can still fix the bug
>> (assuming there is even a bug). It's silly for the rest of us to be
>> sitting around twiddling our thumbs waiting on this.
>>
>> I agree.
>>
>> One other bug is still listed.
>
> I don't think that all of the developers can fruitfully employ
> themselves working exclusively on this particular bug until further
> notice. Starting pretest might result in more bugs to work on being
> detected, making the developers be able to employ their skills in
> parallel towards the release.
In particular, the other remaining bug deals with the coding system
code, about which I for one know nothing.
prev parent reply other threads:[~2006-10-07 2:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 12:05 Starting pretest Richard Stallman
2006-09-24 22:42 ` Kim F. Storm
2006-09-25 10:23 ` Andreas Roehler
2006-09-25 20:48 ` Richard Stallman
2006-09-25 21:33 ` Chong Yidong
2006-09-26 15:41 ` Richard Stallman
2006-09-26 16:02 ` David Kastrup
2006-09-27 18:43 ` Richard Stallman
2006-09-27 19:01 ` David Kastrup
2006-10-02 4:04 ` Richard Stallman
2006-09-25 22:30 ` Kim F. Storm
2006-09-26 20:00 ` Romain Francoise
2006-09-26 3:28 ` Eli Zaretskii
2006-09-26 5:22 ` Stefan Monnier
2006-09-26 18:54 ` Paul Pogonyshev
2006-10-05 18:04 ` Chong Yidong
2006-10-06 6:02 ` Richard Stallman
2006-10-06 14:47 ` Chong Yidong
2006-10-06 15:03 ` Kim F. Storm
2006-10-07 1:07 ` Richard Stallman
2006-10-07 1:17 ` David Kastrup
2006-10-07 2:01 ` Chong Yidong [this message]
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=8764ewsx37.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.