all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: pmr@pajato.com, emacs-devel@gnu.org
Subject: Re: Rmail mbox-format branch
Date: Fri, 10 Sep 2004 14:42:26 +0300	[thread overview]
Message-ID: <01c4972b$Blat.v2.2.2$64073b80@zahav.net.il> (raw)
In-Reply-To: <m3ekla8l1y.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

> Cc: pmr@pajato.com,  emacs-devel@gnu.org
> From: storm@cua.dk (Kim F. Storm)
> Date: Fri, 10 Sep 2004 12:39:37 +0200
> 
> It will probably take a month or two for the emacs developers
> to fix bugs in the unicode branch before starting pretest on 22.1 --
> 
> in the meantime, we can run a pretest for 21.5 bug-fix release if
> necessary.

Okay, but that means we cannot ``immediately'' start pretesting 22.1.

> > Experience also shows that a pretest of a major new release takes
> > several months.  21.1 took more than 6 months, IIRC, and it was used
> > by more people before the pretest than the Unicode branch is now.
> 
> 21.1 was developed within a "closed group".  21.4 has been developed
> in a wide open forum since day 1, and I think that CVS emacs is used
> by MANY users everyday already -- and as such has got more pre-testing
> already than 21.1 ever got!
> 
> So I'm pretty optimistic re. the length of the 21.4 pretest.

I was talking about the length of the pretest of 22.1, not of 21.4.
The unicode branch is developed by a small group as well, I think it's
even smaller than the one who used 21.1 during its development.

> But if we merge the rmail/mbox branch to trunk now, I'm much less
> optimistic :-(

I don't understand why.  Most Emacs suers don't use RMAIL anyway, so
please explain the reasons for your pessimism.

  reply	other threads:[~2004-09-10 11:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09  4:02 Rmail mbox-format branch Richard Stallman
2004-09-09 14:13 ` Stefan
2004-09-09 14:44   ` Paul Michael Reilly
2004-09-09 15:25     ` Stefan
2004-09-09 18:56     ` Eli Zaretskii
2004-09-09 22:19       ` Miles Bader
2004-09-10  7:36         ` Kim F. Storm
2004-09-10  9:18           ` Eli Zaretskii
2004-09-10  9:38             ` Miles Bader
2004-09-10 10:41               ` Kim F. Storm
2004-09-10 11:44                 ` Eli Zaretskii
2004-09-10 11:36               ` Eli Zaretskii
2004-09-10 10:39             ` Kim F. Storm
2004-09-10 11:42               ` Eli Zaretskii [this message]
2004-09-10 12:38                 ` Kim F. Storm
2004-09-10 16:17                   ` Eli Zaretskii
2004-09-11 23:19                     ` Kim F. Storm
2004-09-11 10:52                   ` Richard Stallman
2004-09-11 11:17                     ` Eli Zaretskii
2004-09-11 16:45                     ` Kim F. Storm
2004-09-11  2:49           ` Luc Teirlinck
2004-09-11 18:46             ` Proof-reading manuals (was Re: Rmail mbox-format branch) Kim F. Storm
2004-09-15  1:12               ` Luc Teirlinck
2004-09-16 11:19                 ` Richard Stallman
2004-09-18 22:06                   ` Luc Teirlinck
2004-09-19 11:00                     ` Richard Stallman
2004-09-19 16:29                       ` Proof-reading manuals Kim F. Storm
2004-09-11 10:50       ` Rmail mbox-format branch Richard Stallman
2004-09-11 11:22         ` Eli Zaretskii
2004-09-11 16:57           ` Stefan
2004-09-13  6:59           ` Richard Stallman
2004-09-15 10:25             ` Thien-Thi Nguyen
2004-09-11 13:50         ` Robert J. Chassell
2004-09-13 23:04           ` Richard Stallman
2004-09-10 17:41   ` Richard Stallman
2004-09-10 20:27     ` Alex Schroeder
2004-09-12  9:09       ` 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='01c4972b$Blat.v2.2.2$64073b80@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.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.