From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Emacs <emacs-devel@gnu.org>, Angelo Graziosi <angelo.graziosi@alice.it>
Subject: Re: Bash scripts in black and white
Date: Sat, 15 May 2010 09:56:28 -0400 [thread overview]
Message-ID: <jwvy6fl1dc6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <AANLkTimnc0UGRxAF8_-jjCVTCWcZhB-BhG4x6493NMSv@mail.gmail.com> (Lennart Borgman's message of "Sat, 15 May 2010 00:40:24 +0200")
>> PS. Sometime one gets the idea that Emacs's developers do not test deeply
>> (for example, with at least a clean bootstrap) their changes... This would
>> explain why the bugs tracker is at #6193 :-)
A clean bootstrap is obviously out of the question for me.
OTOH, I'd be happy if someone setup a build robot that constantly tries
to build Emacs, then run some tests, and if they all succeeds updates
a branch. This way we can point people to *that* branch where the
obvious bugs have been filtered. It wouldn't reduce the number of
bug-reports, but it would make reports such as this sh-script one be
machine-generated rather than human-generated, leading maybe to
less frustration.
> If someone has time to add unit tests to Emacs this would be a bit
> better... ;-)
> ert.el with my small additions could handle tests for things like this.
Yes, as I said, I'd be delighted to integrate something like that in
emacs/test.
Stefan
next prev parent reply other threads:[~2010-05-15 13:56 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 [this message]
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
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=jwvy6fl1dc6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/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).