From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus automatic builds
Date: Wed, 20 Apr 2011 15:58:53 -0500 [thread overview]
Message-ID: <87vcy8d4he.fsf@lifelogs.com> (raw)
In-Reply-To: <87sjtcoiz0.fsf@randomsample.de>
On Wed, 20 Apr 2011 20:50:27 +0200 David Engster <deng@randomsample.de> wrote:
DE> Please note that there's one little annoyance: You will get a single
DE> mail for all failed builds, meaning for every Emacs version. That means
DE> if you "really" break something, you'll get 5 mails. There's no way in
DE> buildbot to send just one mail which contains all the information.
I can live with that.
DE> OK, I chose lisp/tests.
DE> The buildbot will not run the NNTP test on new commits. I think the main
DE> part of this test is actually not the nntp testing, but more that it is
DE> an integration test which will fire up various parts of Gnus, so that
DE> broken require's etc. will hopefully pop up during startup.
That's great, thank you!
>> Could this work if we symlink registry.el and gnus-registry.el into the
>> tests directory? Git supports symlinks and it would be a neat hack.
DE> I think this is a bit confusing, since the tests comprise only a small
DE> part of those files. But I have no strong opinion on this.
I meant if you chose to put "tests" at the top level, sorry. The way
you have it now is great.
Ted
next prev parent reply other threads:[~2011-04-20 20:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 4:28 no gnus registry new dependency on ert? Eric Abrahamsen
2011-04-06 10:03 ` Ted Zlatanov
2011-04-06 10:10 ` David Engster
2011-04-06 10:54 ` Ted Zlatanov
2011-04-06 13:10 ` Ted Zlatanov
2011-04-06 13:28 ` David Engster
2011-04-06 14:26 ` Ted Zlatanov
2011-04-06 14:57 ` David Engster
2011-04-06 15:00 ` Ted Zlatanov
2011-04-06 15:03 ` David Engster
2011-04-06 15:51 ` Ted Zlatanov
2011-04-06 13:15 ` Gnus automatic builds (was: no gnus registry new dependency on ert?) Ted Zlatanov
2011-04-06 13:31 ` Gnus automatic builds David Engster
2011-04-06 16:14 ` David Engster
2011-04-06 16:30 ` Ted Zlatanov
2011-04-06 18:10 ` David Engster
2011-04-06 18:57 ` Ted Zlatanov
2011-04-07 19:21 ` David Engster
2011-04-07 19:51 ` Ted Zlatanov
2011-04-07 20:02 ` David Engster
2011-04-07 21:19 ` Ted Zlatanov
2011-04-12 16:08 ` Lars Magne Ingebrigtsen
2011-04-12 16:29 ` David Engster
2011-04-12 16:36 ` Lars Magne Ingebrigtsen
2011-04-12 18:33 ` Jason L Tibbitts III
2011-04-12 18:41 ` Lars Magne Ingebrigtsen
2011-04-12 19:35 ` Jason L Tibbitts III
2011-04-12 19:46 ` David Engster
2011-04-12 19:51 ` Jason L Tibbitts III
2011-04-16 8:22 ` David Engster
2011-04-16 15:19 ` Ted Zlatanov
2011-04-20 18:50 ` David Engster
2011-04-20 20:58 ` Ted Zlatanov [this message]
2011-04-22 11:27 ` Adam Sjøgren
2011-04-22 21:21 ` David Engster
2011-04-25 9:05 ` Adam Sjøgren
2011-04-12 20:00 ` Lars Magne Ingebrigtsen
2011-04-20 20:59 ` David Engster
2011-04-20 21:03 ` Ted Zlatanov
2011-04-20 21:31 ` Jason L Tibbitts III
2011-04-21 7:33 ` David Engster
2011-04-25 12:28 ` Ted Zlatanov
2011-04-06 20:26 ` David Engster
2011-04-07 19:30 ` David Engster
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=87vcy8d4he.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).