all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org, kjambunathan@gmail.com
Subject: RE: Emacs freezes every now and then on my windows 7 pc
Date: Fri, 3 Aug 2012 07:10:09 -0700	[thread overview]
Message-ID: <6056134BD3254EDFA2BCD19B4F8E0790@us.oracle.com> (raw)
In-Reply-To: <831ujocwiu.fsf@gnu.org>

> > 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.

No, this degree of volatility is not expected, if expectation is based on past
experience.  This is not near the mean (or median or mode) of the frequency
distribution, in my guesstimation.

New bugs and disruptions are to be expected, of course.  But this amount of
disruption (at the C level in particular, e.g. crashing) is not typical,
fortunately.

As I think you hinted in emacs-devel, this is more like what everyone might have
experienced if you had developed bidi, from the outset, as the main dish,
instead of as a side dish that later, when more or less perfected, was
incorporated into the main dish.

> I would actually advise people who don't build Emacs themselves
> not to use the development snapshots for anything serious.

Oh, no need to worry.  I wouldn't think of using them for anything serious,
believe me.  (Not that I do anything serious with any build or release.)

And the matter has nothing to do with whether someone builds Emacs personally or
uses a binary built by someone else.  Who builds Emacs is irrelevant here.

And the more frequently prebuilt Windows binaries are provided, the easier and
quicker are the reporting and debugging of bugs.  That's an obvious benefit.
Costs include the effort to build and post the binaries, of course.

> > There seems to be a fair amount of volatility in the C code 
> > at this time....  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.

On n'arrete pas le progres. ;-)




  reply	other threads:[~2012-08-03 14:10 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
2012-08-03 14:10             ` Drew Adams [this message]
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

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

  git send-email \
    --in-reply-to=6056134BD3254EDFA2BCD19B4F8E0790@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --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.
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.