From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Changes that should go into version 24.4
Date: Sat, 22 Mar 2014 10:44:59 +0200 [thread overview]
Message-ID: <83r45u4o6s.fsf@gnu.org> (raw)
In-Reply-To: <532CEDEF.90707@dancol.org>
> Date: Fri, 21 Mar 2014 18:57:03 -0700
> From: Daniel Colascione <dancol@dancol.org>
>
> the subr.el one should be in neither branch. It papers over a
> release-blocking bug. We shouldn't release 24.4 until we've figured
> out why the hell the GC randomly crashes. You can't even be sure
> that your lisp hack even fixes the problem.
Since (evidently) no one is actively works on fixing that bug, I see
no reasons to punish people who run the trunk codebase by imposing on
them random crashes they cannot recover from. As long as the bug
remains open, we didn't forget about it, and will fix it eventually;
in the meantime, let users have one less reason for crashes.
next prev parent reply other threads:[~2014-03-22 8:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 1:47 Changes that should go into version 24.4 Richard Stallman
2014-03-22 1:57 ` Daniel Colascione
2014-03-22 8:44 ` Eli Zaretskii [this message]
2014-03-22 8:50 ` Daniel Colascione
2014-03-22 9:24 ` Eli Zaretskii
2014-03-22 9:08 ` Eli Zaretskii
2014-03-22 9:15 ` Daniel Colascione
2014-03-22 23:57 ` Richard Stallman
2014-03-23 1:58 ` GC bug investigation Daniel Colascione
2014-03-23 2:13 ` Daniel Colascione
2014-03-23 14:56 ` Richard Stallman
2014-03-23 14:57 ` Richard Stallman
2014-03-23 15:15 ` David Kastrup
2014-03-24 15:01 ` Richard Stallman
2014-03-23 15:22 ` Daniel Colascione
2014-03-23 16:14 ` Andreas Schwab
2014-03-24 15:01 ` Richard Stallman
2014-03-23 16:20 ` Eli Zaretskii
2014-03-23 3:57 ` Changes that should go into version 24.4 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
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=83r45u4o6s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--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).