From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Release schedule
Date: Mon, 23 Apr 2007 07:56:23 +0900 [thread overview]
Message-ID: <E1Hfkyk-00012N-W3@etlken.m17n.org> (raw)
In-Reply-To: <ufy6tgl7w.fsf@gnu.org> (message from Eli Zaretskii on Sun, 22 Apr 2007 06:08:03 +0300)
In article <ufy6tgl7w.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > Cc: rms@gnu.org, emacs-devel@gnu.org
> > From: Chong Yidong <cyd@stupidchicken.com>
> > Date: Sat, 21 Apr 2007 15:25:20 -0400
> >
> > We know exactly what patches went into the tree, and that they are not
> > risky. So I think the situation is OK.
> In software, you can never know such things for certain, and the more
> changes you make, the less certain you are in the outcome.
> So I think we need another pretest, but if I'm the only one, so be it.
I agree with Eli on this matter.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-04-22 22:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 21:53 Release schedule Richard Stallman
2007-04-21 3:38 ` Chong Yidong
2007-04-21 10:11 ` Eli Zaretskii
2007-04-21 19:25 ` Chong Yidong
2007-04-21 20:02 ` Glenn Morris
2007-04-21 20:14 ` Chong Yidong
2007-04-21 20:17 ` Glenn Morris
2007-04-21 22:31 ` Nick Roberts
2007-04-21 23:02 ` Glenn Morris
2007-04-22 3:08 ` Eli Zaretskii
2007-04-22 8:11 ` Juanma Barranquero
2007-04-22 10:33 ` Kim F. Storm
2007-04-22 11:13 ` David Kastrup
2007-04-23 3:48 ` Richard Stallman
2007-04-23 5:13 ` Stefan Monnier
2007-04-23 6:12 ` David Kastrup
2007-04-22 11:51 ` Romain Francoise
2007-04-22 14:20 ` Chong Yidong
2007-04-22 22:56 ` Kenichi Handa [this message]
2007-04-22 16:35 ` Richard Stallman
2007-04-22 20:42 ` Eli Zaretskii
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=E1Hfkyk-00012N-W3@etlken.m17n.org \
--to=handa@m17n.org \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--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 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).