From: David Engster <deng@randomsample.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Gnus automatic builds
Date: Wed, 06 Apr 2011 15:31:25 +0200 [thread overview]
Message-ID: <m2ei5fzetu.fsf@randomsample.de> (raw)
In-Reply-To: <87r59fr05z.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 06 Apr 2011 08:15:20 -0500")
Ted Zlatanov writes:
> On Wed, 06 Apr 2011 12:28:17 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
> EA> The recent registry rewrite has introduced a dependency on the ERT
> EA> testing library -- that library is part of emacs 24 but not emacs 23.
> EA> That made for an awkward code update, is there any way to warn people of
> EA> what's happening, or even include a local installation of ERT for those
> EA> who don't have it already?
>
> To answer the implied question, "how do we catch version compatibility
> and other commit errors," I think the right way is with automatic builds
> against various Emacs and XEmacs versions. David Engster was planning
> to set something up and he was talking to Lars last I heard. David, if
> you need anything from me, please let me know. I'm eager to get
> automatic builds working for the benefit of Gnus and Emacs as a whole.
There are only a few changes needed to dgnushack and the Makefiles. I
think I can do this quickly later today.
-David
next prev parent reply other threads:[~2011-04-06 13:31 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 ` David Engster [this message]
2011-04-06 16:14 ` Gnus automatic builds 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
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=m2ei5fzetu.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--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.
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).