unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin)
Date: Sat, 12 Apr 2008 11:30:07 +0300	[thread overview]
Message-ID: <u7if3a31s.fsf@gnu.org> (raw)
In-Reply-To: <4800687C.8090708@alice.it>

> Date: Sat, 12 Apr 2008 09:45:00 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> 
> cd emacs
> ./configure
> make bootstrap
> 
> 
> Yes, it is heavy, but it is the only clean method that will guarantee 
> the patches do no introduce regressions.

Actually, there is no practical way to know for sure that changes
don't introduce regressions, in general.  While "make bootstrap" will
make sure a bootstrap works on the submitter's machine (and is
recommended to those that can afford it), it says nothing about other
ways of building Emacs, nor about other machines and OSes we support.
It also doesn't tell anything about run-time behavior, and as long as
we don't have a test suite, there will always be a significant doubt.
(Even when we do have a test suite, we cannot ask contributors to run
it on more than one system -- her own.)

IOW, I submit that asking people to be sure they don't cause
regressions in these circumstances is tantamount to asking them not to
commit changes at all.

So please calm down.  The development trunk will inevitably become
broken from time to time, no matter what.  If you must build the trunk
every day or even more frequently, and depend on the resulting binary
for your daily work, I suggest to make some arrangements to have the
previous working build available until you are sure the new one builds
and works successfully.




  reply	other threads:[~2008-04-12  8:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  9:06 Bootstrapping Emacs-23.0.60-trunk still fails (GNU/Linux, Cygwin) Angelo Graziosi
2008-04-12  7:45 ` Bootstrapping Emacs-23.0.60-trunk newly broken " Angelo Graziosi
2008-04-12  8:30   ` Eli Zaretskii [this message]
2008-04-12  9:18     ` Angelo Graziosi
2008-04-12  9:27       ` Juanma Barranquero
2008-04-12 11:46         ` Romain Francoise
2008-04-12 12:12           ` Juanma Barranquero
2008-04-12 12:16           ` martin rudalics
2008-04-12 13:41             ` Romain Francoise
2008-04-12 12:53           ` martin rudalics
2008-04-13  9:31             ` Romain Francoise
2008-04-13 14:03               ` Eli Zaretskii
2008-04-14  0:52               ` Richard Stallman
2008-04-12 13:45           ` Stefan Monnier
2008-04-12 14:06           ` Jason Rumney
2008-04-12 14:24           ` Eric Hanchrow
2008-04-12 10:08       ` Eli Zaretskii
2008-04-12  9:28   ` 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=u7if3a31s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.graziosi@alice.it \
    --cc=emacs-devel@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).