From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Bash scripts in black and white
Date: Sat, 15 May 2010 11:20:39 +0200 [thread overview]
Message-ID: <4BEE6767.5090607@alice.it> (raw)
In-Reply-To: <AANLkTikE90qX3x-mN3MjZzc7LbZj9eR0bbMxLNHU1d2d@mail.gmail.com>
Il 15/05/2010 11.12, Juanma Barranquero ha scritto:
> On Sat, May 15, 2010 at 10:15, Angelo Graziosi<angelo.graziosi@alice.it> wrote:
>
>> Often the bugs come from lack of bootstrap, and bootstrap (+PDF manual,
>> +tar.xz of the binary distribution) takes about 25 minutes on Cygwin, which
>> is only an emulator...
>
> Bootstrap failures are few and far between, so half an hour* to test
> every change is a waste of resources**. In any case, bootstrap
> failures are usually detected and fixed in a few hours.
I did not refer to bootstrap failure! and not to bootstrap at every
changes. At least once per week or when there are many many changes:
catching a bug soon is better than after some time :-)
>
> *: Not everyone has powerful, up-to-date computers.
My PC was born on September 2007! with the same XP!
> **: I *do* bootstrap almost daily; but I don't think it should be
> forced on everyone. If we wanted such an always-buildable,
> always-runable repository, we would be better served by a continuous
> integration setup. I don't think we want, though.
See above.
Ciao,
Angelo.
next prev parent reply other threads:[~2010-05-15 9:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 9:16 Bash scripts in black and white Angelo Graziosi
2010-05-14 12:16 ` Thierry Volpiatto
2010-05-14 19:29 ` Stefan Monnier
2010-05-14 19:58 ` Thierry Volpiatto
2010-05-14 21:23 ` Angelo Graziosi
2010-05-14 22:40 ` Lennart Borgman
2010-05-15 5:30 ` joakim
2010-05-15 13:56 ` Stefan Monnier
2010-06-27 14:21 ` Christian Ohler
2010-05-15 6:33 ` Eli Zaretskii
2010-05-15 8:15 ` Angelo Graziosi
2010-05-15 9:12 ` Juanma Barranquero
2010-05-15 9:20 ` Angelo Graziosi [this message]
2010-05-15 9:34 ` Juanma Barranquero
2010-05-15 11:43 ` Angelo Graziosi
2010-05-15 9:51 ` Leo
2010-05-15 12:11 ` Eli Zaretskii
2010-05-15 12:49 ` martin rudalics
2010-05-15 13:05 ` Leo
2010-05-15 17:12 ` Romain Francoise
2010-05-16 18:38 ` Ken Raeburn
2010-06-24 17:58 ` Ted Zlatanov
2010-06-24 22:11 ` Stefan Monnier
2010-06-25 5:18 ` Thierry Volpiatto
2010-06-26 22:23 ` Stefan Monnier
2010-06-27 5:09 ` Thierry Volpiatto
2010-06-30 18:26 ` buildbot setup (was: Bash scripts in black and white) Ted Zlatanov
2010-06-30 18:39 ` Lennart Borgman
2010-06-30 19:06 ` buildbot setup Ted Zlatanov
2010-06-30 21:34 ` Lennart Borgman
2010-07-01 13:00 ` Ted Zlatanov
2010-07-01 13:08 ` Lennart Borgman
2010-07-01 1:43 ` Stefan Monnier
2010-07-01 4:32 ` Stephen J. Turnbull
2010-07-04 21:26 ` Stefan Monnier
2010-07-04 22:56 ` joakim
2010-05-15 10:36 ` Bash scripts in black and white Thierry Volpiatto
2010-05-17 19:45 ` Stephen Eilert
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=4BEE6767.5090607@alice.it \
--to=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).