all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: unicode-2 and multitty (was: html-mode demanding <html> a bit too tight)
Date: Fri, 04 May 2007 11:13:27 +0200	[thread overview]
Message-ID: <86vef90x54.fsf_-_@lola.quinscape.zz> (raw)
In-Reply-To: <E1Hie3S-0001xj-Ln@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 30 Apr 2007 18\:09\:10 -0400")

Richard Stallman <rms@gnu.org> writes:

>     FWIW, I will not contribute any further to Emacs development
>     until Emacs 22.1 has been officially released.
>
> I appreciate your past contributions, and I regret your departure.
> I hope you will be back some day.

This ominous remark makes little sense unless there is no intent of
actually releasing Emacs 22.1 in the foreseeable future.

So the question is what developers who don't want to be party to the
release farce are supposed to do if they don't want to let Emacs
development fall into obsolescence.

While the release is "imminent", letting HEAD and the release branch
diverge would likely be impolite.  So what work is there to be done?

The roadmap called more or less for merging the multitty branch and
the unicode-2 branch "after the release".  There is probably no
necessity in doing this kind of work in HEAD.  It should likely be
possible to already do this in unicode-2.  The disadvantage would be
that it will become somewhat more work to keep changes in HEAD
synchronized to unicode-2, but the multitty branch was supposed to be
confined to a rather small number of places.

Doing this now will work towards a timely release of Emacs 23.1, and
it would appear that there is little sense in freezing the Emacs 23.1
process just because 22.1 is stalling.

So for those who have gotten tired investing energy and focus into the
release of 22.1 (and there remains little enough in the way of
_possibilities_ to invest them there), maybe it would be a possibility
to switch to the unicode-2 branch, and also work on the merge of
multitty.

I know that there are a few prepacked "Emacs-23" variants around:
would it be acceptable to the maintainers of those if the unicode-2
branch were to go through a period of relative instability caused by
the merge of multitty?

Would it be better etiquette to create or use a different mailing list
than this one for discussing such work on the unicode-2 branch?

Thanks,

-- 
David Kastrup

  reply	other threads:[~2007-05-04  9:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87647ooxwm.fsf@zip.com.au>
     [not found] ` <jwvps5vry60.fsf-monnier+emacs@gnu.org>
     [not found]   ` <462CC030.8030203@gmail.com>
     [not found]     ` <87mz0y8vyk.fsf@zip.com.au>
2007-04-25 14:51       ` html-mode demanding <html> a bit too tight Richard Stallman
2007-04-25 17:36         ` Stefan Monnier
2007-04-25 18:18           ` Lennart Borgman (gmail)
2007-04-27  5:59           ` Richard Stallman
2007-04-26  4:11         ` Glenn Morris
2007-04-27  5:59           ` Richard Stallman
2007-04-27  6:22             ` David Kastrup
2007-04-27 13:08               ` Eli Zaretskii
2007-04-27 10:27             ` Kim F. Storm
2007-04-27 11:14               ` Lennart Borgman (gmail)
2007-04-27 11:41                 ` David Kastrup
2007-04-27 11:49                   ` Lennart Borgman (gmail)
2007-04-27 11:56                     ` David Kastrup
2007-04-27 12:03                       ` Lennart Borgman (gmail)
2007-04-27 12:22                         ` David Kastrup
2007-04-27 21:41                           ` Lennart Borgman (gmail)
2007-04-27 12:48                 ` Eli Zaretskii
2007-04-27 14:11                   ` David Reitter
2007-04-27 20:17                   ` Lennart Borgman (gmail)
2007-04-27 20:53                     ` Chong Yidong
2007-04-27 21:02                       ` Lennart Borgman (gmail)
2007-04-27 18:58                 ` Edward O'Connor
2007-04-27 12:53               ` Eli Zaretskii
2007-04-27 20:53                 ` Kim F. Storm
2007-04-28  4:06               ` Richard Stallman
2007-04-28 13:59                 ` David Kastrup
2007-04-28 14:20                 ` Juanma Barranquero
2007-04-29 21:17                 ` Kim F. Storm
2007-04-30 22:09                   ` Richard Stallman
2007-05-04  9:13                     ` David Kastrup [this message]
2007-05-04  9:41                       ` unicode-2 and multitty Jason Rumney
2007-05-04 10:14                         ` David Kastrup
2007-05-04 20:46                           ` Kim F. Storm
2007-05-05  0:26                             ` David Kastrup
2007-05-05 21:54                             ` Stefan Monnier
2007-05-07  9:55                               ` Kim F. Storm
2007-05-07 10:09                                 ` David Kastrup
2007-05-04  9:42                       ` Ulrich Mueller
2007-05-04 10:39                       ` unicode-2 and multitty (was: html-mode demanding <html> a bit too tight) Eli Zaretskii
2007-05-04 11:12                         ` unicode-2 and multitty David Kastrup
2007-05-04 21:18                       ` unicode-2 and multitty (was: html-mode demanding <html> a bit too tight) Richard Stallman
2007-05-05  0:17                         ` unicode-2 and multitty David Kastrup
2007-04-27 11:17             ` html-mode demanding <html> a bit too tight Leo
2007-04-27 19:51             ` Glenn Morris
2007-04-28  4:07               ` Richard Stallman
2007-04-28  8:04               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86vef90x54.fsf_-_@lola.quinscape.zz \
    --to=dak@gnu.org \
    --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 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.