unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Angelo Graziosi" <angelo.graziosi@alice.it>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin)
Date: Sat, 12 Apr 2008 11:27:34 +0200	[thread overview]
Message-ID: <f7ccd24b0804120227i43f2298fvdbe828879b1fbd5e@mail.gmail.com> (raw)
In-Reply-To: <48007E59.7040805@alice.it>

On Sat, Apr 12, 2008 at 11:18 AM, Angelo Graziosi
<angelo.graziosi@alice.it> wrote:

>  But how could the trunk users to test a new patch if it breaks the
> bootstrap?

There is no need to bootstrap after every cvs update...

>  I thought that passing the bootstrap was the minimal request for submitting
> a patch and that this would be reached if all start with the same conditions
> in bootstrapping.

In an ideal world, it'd be nice if each change were to be known not to
break bootstrapping. But the fact is, most patches do not break it
[1], and the ones that do are usually detected quite fast, so it is a
waste of resources to require everyone to bootstrap before each commit
[2].

[1] Some changes (configure, makefiles, autoloads, etc.) are more
likely than others; we're hit such a spot right now :(
[2] Bear in mind that tiny, apparently trivial changes can break it:
there's no complexity threshold below which a change is totally safe.

 Juanma




  reply	other threads:[~2008-04-12  9:27 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
2008-04-12  9:18     ` Angelo Graziosi
2008-04-12  9:27       ` Juanma Barranquero [this message]
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=f7ccd24b0804120227i43f2298fvdbe828879b1fbd5e@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --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).