all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Cruise Control to mitigate failure in make bootstrap?
Date: Sat, 12 Apr 2008 16:51:59 +0000	[thread overview]
Message-ID: <20080412165159.GA1771@muc.de> (raw)
In-Reply-To: <4800C111.3090407@gnu.org>

On Sat, Apr 12, 2008 at 03:02:57PM +0100, Jason Rumney wrote:
> Alan Mackenzie wrote:
> >I have used this product in one of my day jobs, and it works well.

> I suspect it works well in a day job environment, when you are working
> for the same 8 hours a day as the other developers on the project.  I
> suspect it works less well for Free Software where volunteers might
> have a haf hour to spare so they fix a bug, don't have time to do a
> full bootstrap before checking in, then might not see any mail
> generated because they are offline for the weekend.

Well, it wouldn't be worse than what we currently have.

Having seen the program (which is free software, after all) work so well,
I think it would work just as well for the Emacs project.  How long would
a make bootstrap take on a suitable server?  10 minutes?  Possibly 2
minutes?  That's not terribly long to wait to check that a change just
committed hasn't fouled things up.

I've just a look at my emacs-devel archive, and since mid January 2008,
there are 26 threads with subject line "bootstrap fails".  That's an
awful lot of inconvenience to an awful lot of people.

-- 
Alan Mackenzie (Nuremberg, Germany).




  parent reply	other threads:[~2008-04-12 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 10:48 Cruise Control to mitigate failure in make bootstrap? Alan Mackenzie
2008-04-12 14:02 ` Jason Rumney
2008-04-12 15:38   ` aaditya sood
2008-04-12 16:51   ` Alan Mackenzie [this message]
2008-04-13 20:22   ` Bob Rogers
2008-04-12 19:16 ` Stefan Monnier

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=20080412165159.GA1771@muc.de \
    --to=acm@muc.de \
    --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 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.