From: storm@cua.dk (Kim F. Storm)
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: doc patch: "Saving Properties" merge into "Format Conversion"
Date: Thu, 03 May 2007 11:14:45 +0200 [thread overview]
Message-ID: <m3fy6e8e0q.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <f7ccd24b0705030130w60031695he516292124ded46@mail.gmail.com> (Juanma Barranquero's message of "Thu\, 3 May 2007 10\:30\:01 +0200")
"Juanma Barranquero" <lekktu@gmail.com> writes:
"Juanma Barranquero" <lekktu@gmail.com> writes:
> On 5/3/07, Richard Stallman <rms@gnu.org> wrote:
>
>> We might use the trunk to make Emacs 22.2.
What a wonderful idea! Soooo completely illogical and out of sync
with any release procedure (that actually aims are making progress
towards a release).
>
> Why? What would be the advantage of using the trunk for 22.2 instead
> of the EMACS_22_BASE branch?
His statement above and the current talks about merging the RMAIL mbox
branch (which IIUC don't really have a current maintainer) could
indicate that RMS wants to make a 22.2 release which includes just the
Rmail branch...
>
> There is at least one specific disadvantage, i.e., it would delay
> merging the unicode and multi-tty branches onto the trunk.
Indeed!
I'm not usually paranoid, but isn't this just another strong
indication of the secret(?) plan to delay -- as much as possible --
not just 22.1, but also every possible future release.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2007-05-03 9:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 8:15 doc patch: "Saving Properties" merge into "Format Conversion" Thien-Thi Nguyen
2007-05-01 17:25 ` Richard Stallman
2007-05-02 9:28 ` Thien-Thi Nguyen
2007-05-02 17:44 ` Richard Stallman
2007-05-02 19:34 ` Stefan Monnier
2007-05-02 19:50 ` Thien-Thi Nguyen
2007-05-03 2:02 ` Richard Stallman
2007-05-03 2:19 ` Nick Roberts
2007-05-03 8:30 ` Juanma Barranquero
2007-05-03 9:14 ` Kim F. Storm [this message]
2007-05-03 23:55 ` Richard Stallman
2007-05-04 1:00 ` Nick Roberts
2007-05-04 7:57 ` Juanma Barranquero
2007-05-04 21:17 ` Richard Stallman
2007-05-04 23:05 ` Kim F. Storm
2007-05-05 23:18 ` Richard Stallman
2007-05-05 0:03 ` Nick Roberts
2007-05-05 23:18 ` Richard Stallman
2007-05-06 0:04 ` David Kastrup
2007-05-06 0:56 ` Nick Roberts
2007-05-06 4:51 ` Miles Bader
2007-05-06 7:37 ` David Kastrup
2007-05-06 11:05 ` Jan Djärv
2007-05-06 11:37 ` David Kastrup
2007-05-06 10:53 ` Juanma Barranquero
2007-05-06 11:17 ` Miles Bader
2007-05-06 11:56 ` Juanma Barranquero
2007-05-06 12:22 ` David Kastrup
2007-05-06 12:51 ` Miles Bader
2007-05-06 14:25 ` Juanma Barranquero
2007-05-06 22:26 ` Richard Stallman
2007-05-07 2:41 ` Stefan Monnier
2007-05-06 16:50 ` Eli Zaretskii
2007-05-06 22:25 ` Richard Stallman
2007-05-07 9:38 ` Thien-Thi Nguyen
2007-05-04 20:50 ` Kim F. Storm
2007-05-03 9:59 ` Thien-Thi Nguyen
2007-05-03 23:55 ` Richard Stallman
2007-05-04 9:14 ` Thien-Thi Nguyen
2007-05-03 13:55 ` Stefan Monnier
2007-05-07 15:59 ` Kevin Ryde
2007-05-08 20:21 ` Thien-Thi Nguyen
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=m3fy6e8e0q.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--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).