From: Eli Zaretskii <eliz@gnu.org>
To: raman@users.sourceforge.net
Cc: raman@users.sourceforge.net, andreas.roehler@online.de,
emacs-devel@gnu.org
Subject: Re: Experimental features
Date: Sun, 24 Jun 2007 21:42:15 +0300 [thread overview]
Message-ID: <uwsxtnqig.fsf@gnu.org> (raw)
In-Reply-To: <18045.60441.244911.539225@gargle.gargle.HOWL> (raman@users.sf.net)
> Date: Sat, 23 Jun 2007 20:59:21 -0700
> From: "T. V. Raman" <raman@users.sf.net>
> Cc: emacs-devel@gnu.org, andreas.roehler@online.de, raman@users.sourceforge.net
>
> That is an advantage because as we have seen with the transition
> from emacs 21.4 to 22, it takes a *long* time for a major Emacs
> version to come out --- and with good reason, since stability of
> Emacs is important to all of us.
That is a reason to make Emacs releases shorter, not to release
packages separately.
> But that also means that smaller packages will --- and *should*
> be allowed to --- evolve faster.
I don't quite see the logic of this conclusion. If Emacs must be
stable, so do the packages that come with it.
next prev parent reply other threads:[~2007-06-24 18:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 21:05 Experimental features Stefan Monnier
2007-06-22 21:22 ` Lennart Borgman (gmail)
2007-06-23 4:15 ` Stefan Monnier
2007-06-23 12:40 ` Thien-Thi Nguyen
2007-06-23 19:07 ` Stefan Monnier
2007-06-23 2:51 ` dhruva
2007-06-23 6:00 ` Andreas Röhler
2007-06-24 1:43 ` T. V. Raman
2007-06-24 3:02 ` Eli Zaretskii
2007-06-24 3:59 ` T. V. Raman
2007-06-24 18:42 ` Eli Zaretskii [this message]
2007-06-23 13:19 ` Richard Stallman
2007-06-23 13:37 ` Juanma Barranquero
2007-06-24 14:40 ` Richard Stallman
2007-06-24 14:53 ` Juanma Barranquero
2007-06-24 19:25 ` Stefan Monnier
2007-06-23 19:16 ` Stefan Monnier
2007-06-24 14:41 ` Richard Stallman
2007-06-24 19:23 ` Stefan Monnier
2007-06-24 23:47 ` Richard Stallman
2007-06-28 18:51 ` Stefan Monnier
2007-06-29 19:33 ` 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
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=uwsxtnqig.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=raman@users.sourceforge.net \
/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).