unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 17:27:52 +0300	[thread overview]
Message-ID: <83k3xgaw47.fsf@gnu.org> (raw)
In-Reply-To: <6056134BD3254EDFA2BCD19B4F8E0790@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <kjambunathan@gmail.com>, <help-gnu-emacs@gnu.org>
> Date: Fri, 3 Aug 2012 07:10:09 -0700
> 
> > > 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.

Maybe so, but then you need to adapt your expectations to the changing
reality.

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

It is relevant, because once a fix is committed, people who build
themselves can rebuild and have a stable binary.

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

Volunteers to provide daily snapshots are welcome.



  reply	other threads:[~2012-08-03 14:27 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
2012-08-03 14:27               ` Eli Zaretskii [this message]
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=83k3xgaw47.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).