unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Automatic bootstrap
Date: Fri, 20 Jun 2008 02:46:58 -0400	[thread overview]
Message-ID: <E1K9aOg-0007xB-9p@fencepost.gnu.org> (raw)
In-Reply-To: <48590F58.4020201@gnu.org> (message from Jason Rumney on Wed, 18 Jun 2008 14:36:24 +0100)

    > A week or so there was a discussion about the inconvenience of the
    > existence of `make bootstrap'.  I suggested that we create a source
    > file bootstrap.el whose compiled file, bootstrap.elc, would control
    > whether `make emacs' does a bootstrap or not.  We could also change
    > bootstrap.el trivially after installing any change which we think
    > makes it advisable for testers to bootstrap afresh.
    >   

    I don't think it will work, as developers who make changes that make it 
    advisable to bootstrap would forget to change that file.

Indeed, that might happen.  But is that a reason to reject the idea?
I don't think so.  Even if things are not perfect, they will be better.

     Other 
    developers might change it needlessly, causing testers with low end 
    hardware unnecessary pain.

I don't think that is likely to happen very often.
People have no reason to do this.





  parent reply	other threads:[~2008-06-20  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 13:17 Automatic bootstrap Richard M Stallman
2008-06-18 13:36 ` Jason Rumney
2008-06-19 13:58   ` Stefan Monnier
2008-06-20  6:46   ` Richard M Stallman [this message]
2008-06-19  7:50 ` Paul Michael Reilly
2008-06-19 18:15   ` Richard M Stallman
2008-06-20  2:20     ` Miles Bader
2008-06-20 19:28       ` Richard M Stallman

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=E1K9aOg-0007xB-9p@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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).