unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@iwi.uni-sb.de>
Cc: miles@gnu.org, Adrian Robert <arobert@cogsci.ucsd.edu>,
	snogglethorpe@gmail.com, emacs-devel@gnu.org
Subject: Re: Release timelines and Unicode2 branch
Date: Tue, 13 Sep 2005 13:51:43 +0200	[thread overview]
Message-ID: <E1EF9KB-0003uB-Qz@iwi191.iwi.uni-sb.de> (raw)
In-Reply-To: <17190.42651.597245.266518@farnswood.snap.net.nz> (Nick Roberts's message of "Tue, 13 Sep 2005 22:14:51 +1200")

* Nick Roberts (2005-09-13) writes:

>  > > That does beg the question as to why unicode-2 hasn't already been
>  > > merged into HEAD given that, using timescales for Emacs 22, Emacs 23
>  > > won't be released until about 2010.
>  > 
>  > So that Emacs 22 will not get released only in 2010.
>
> The description Miles gave suggested that unicode-2 was already usable.

That depends on your definition of "usable".  Last time I tried the
unicode-2 branch it felt significantly slower than a trunk build,
observable e.g. during line-by-line scrolling.  The slowdown was big
enough for me to stick with a trunk build.

-- 
Ralf

  parent reply	other threads:[~2005-09-13 11:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 18:43 Release timelines and Unicode2 branch Adrian Robert
2005-09-12 19:35 ` Stefan Monnier
2005-09-12 20:36   ` Chong Yidong
2005-09-12 21:28     ` David Kastrup
2005-09-12 21:31     ` Kim F. Storm
2005-09-12 21:37     ` Stefan Monnier
2005-09-13  3:31       ` Eli Zaretskii
2005-09-13  0:47     ` Juanma Barranquero
2005-09-13  5:39     ` Romain Francoise
2005-09-13 17:34       ` Emilio Lopes
2005-09-13 19:52         ` Romain Francoise
2005-09-14 19:58           ` Emilio Lopes
2005-09-15  0:15           ` Chong Yidong
2005-09-14 18:21             ` Romain Francoise
2005-09-13 15:55     ` Richard M. Stallman
2005-09-17 18:22     ` Romain Francoise
2005-09-13 14:26   ` Adrian Robert
2005-09-12 23:22 ` Miles Bader
2005-09-13  0:11   ` Nick Roberts
2005-09-13  1:38     ` Miles Bader
2005-09-13  6:33     ` David Kastrup
2005-09-13 10:14       ` Nick Roberts
2005-09-13 10:44         ` David Kastrup
2005-09-13 11:51         ` Ralf Angeli [this message]
2005-09-13 12:03   ` Adrian Robert
2005-09-13 15:55   ` Richard M. Stallman
2005-09-13 16:25     ` Stefan Monnier
2005-09-14 14:07       ` Richard M. Stallman
2005-09-14 14:38       ` Adrian Robert
2005-09-14 15:43         ` Stefan Monnier
2005-09-15 13:00         ` Richard M. Stallman
2005-09-20  0:14           ` Adrian Robert
2005-09-20  5:23             ` David Kastrup
2005-09-21  6:43             ` Richard M. Stallman
2005-09-22  6:03               ` Steven Tamm
2005-09-22 11:53                 ` Adrian Robert
2005-09-22 15:17                 ` Stefan Monnier
2005-09-23  7:24                 ` Richard M. Stallman
2005-09-13 15:55 ` 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=E1EF9KB-0003uB-Qz@iwi191.iwi.uni-sb.de \
    --to=angeli@iwi.uni-sb.de \
    --cc=arobert@cogsci.ucsd.edu \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=snogglethorpe@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).