From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Romain Francoise <romain@orebokech.com>, emacs-devel@gnu.org
Subject: Re: eshell-defgroup. Do we really need this?
Date: Thu, 31 Jul 2008 21:18:49 +0200 [thread overview]
Message-ID: <48921019.6030308@gmail.com> (raw)
In-Reply-To: <86myjx3lt8.fsf@lifelogs.com>
Ted Zlatanov wrote:
> On Tue, 29 Jul 2008 22:27:54 +0000 Alan Mackenzie <acm@muc.de> wrote:
>
> AM> Why won't our CVS head build NEARLY ALL THE TIME!!!
>
> It's not hard to set up automated builds; I wouldn't use something like
> CruiseControl but a simple tool like buildbot or even a shell script
> would be nice (cvs up && configure && make bootstrap etc) Failure
> notifications can be sent to a central server and more than N (maybe 5?)
> failures in the same place would trigger a bug report or some other
> notification.
>
> CPAN has a nice way to do this with a whole network of testers, so when
> you submit a module failed tests go back to you.
>
> Sorry if this has been discussed before but I didn't see such a thread.
It was discussed before, but I do not know what happened then
http://lists.gnu.org/archive/html/emacs-devel/2008-04/msg01011.html
next prev parent reply other threads:[~2008-07-31 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:27 eshell-defgroup. Do we really need this? Alan Mackenzie
2008-07-31 19:17 ` Ted Zlatanov
2008-07-31 19:18 ` Lennart Borgman (gmail) [this message]
2008-08-01 15:34 ` Ted Zlatanov
2008-08-01 17:08 ` Romain Francoise
2008-08-01 20:30 ` Ted Zlatanov
2008-08-02 4:18 ` Stephen J. Turnbull
2008-08-04 16:34 ` Ted Zlatanov
2008-08-04 17:49 ` Stephen J. Turnbull
2008-08-04 18:38 ` Ted Zlatanov
2008-08-05 8:20 ` Stephen J. Turnbull
2008-08-05 13:57 ` buildbots (was: eshell-defgroup. Do we really need this?) Ted Zlatanov
2008-08-05 20:25 ` Stephen J. Turnbull
2008-08-08 15:26 ` place to send build failure reports? (was: buildbots) Ted Zlatanov
2008-08-08 15:58 ` place to send build failure reports? Chong Yidong
2008-08-03 19:02 ` eshell-defgroup. Do we really need this? Romain Francoise
2008-08-04 16:31 ` Ted Zlatanov
2008-08-01 16:10 ` Progress: " Alan Mackenzie
2008-08-07 19:25 ` 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
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=48921019.6030308@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
--cc=tzz@lifelogs.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).