From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org, kjambunathan@gmail.com
Subject: Re: Emacs freezes every now and then on my windows 7 pc
Date: Fri, 03 Aug 2012 09:36:09 +0300 [thread overview]
Message-ID: <831ujocwiu.fsf@gnu.org> (raw)
In-Reply-To: <1B758CD9545840F1A7FA3D6786813465@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Thu, 2 Aug 2012 16:23:47 -0700
>
> I think several of us have been having the same or similar problems. FWIW, I
> have only been able to use the last release (24.1) for quite a while now. Some
> bugs, including crashes, get fixed, but new ones (including crashes) are
> engendered.
>
> Each week I hope for a new Windows build that works enough to check the fix for
> some bug I filed for a previous build. But in some cases I have not been able
> to check fixes because of new bugs (including crashes). And the Windows builds
> are no longer done weekly, it seems, which aggravates this problem.
Again, this is expected. I would actually advise people who don't
build Emacs themselves not to use the development snapshots for
anything serious.
> There seems to be a fair amount of volatility in the C code at this time. Just
> a guess, based on what I see going by in emacs-devel (without paying too much
> attention) and what I see in the (Windows) builds I try to use.
>
> This is, fortunately, not typical of Emacs development; it is presumably
> temporary. Let's hope things settle down soon.
Sorry, but I'm afraid this is here to stay, at least for a while.
There are a few contributors to Emacs who tend to make disruptive
commits at least once a week. I see no signs that they will stop any
time soon. The only time these attitudes can be kept in check is
during a pretest, or a feature freeze.
next prev parent reply other threads:[~2012-08-03 6:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 14:14 Emacs freezes every now and then on my windows 7 pc C K Kashyap
2012-06-24 14:22 ` Drew Adams
[not found] ` <mailman.3368.1340547787.855.help-gnu-emacs@gnu.org>
2012-08-02 20:05 ` jane.harvill
2012-08-02 20:14 ` Eli Zaretskii
2012-08-02 21:37 ` Tom Davey
2012-08-02 22:05 ` Jambunathan K
2012-08-02 23:23 ` Drew Adams
2012-08-03 6:36 ` Eli Zaretskii [this message]
2012-08-03 14:10 ` Drew Adams
2012-08-03 14:27 ` Eli Zaretskii
2012-08-03 14:39 ` Óscar Fuentes
2012-08-03 14:58 ` Ludwig, Mark
2012-08-03 15:23 ` Óscar Fuentes
2012-08-03 17:57 ` Ludwig, Mark
[not found] ` <mailman.6249.1344003031.855.help-gnu-emacs@gnu.org>
2012-08-04 2:53 ` Jason Rumney
2012-08-04 5:47 ` Drew Adams
2012-08-03 6:31 ` Eli Zaretskii
[not found] ` <mailman.6201.1343943457.855.help-gnu-emacs@gnu.org>
2012-08-03 10:00 ` Hilary
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=831ujocwiu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=kjambunathan@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.
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).