From: Michael Albinus <michael.albinus@gmx.de>
To: joakim@verona.se
Cc: Emacs developers <emacs-devel@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Another Emacs build-server
Date: Sun, 19 Apr 2015 19:51:11 +0200 [thread overview]
Message-ID: <87a8y49fcg.fsf@gmx.de> (raw)
In-Reply-To: <m31tjg9g2z.fsf@exodia.verona.se> (joakim@verona.se's message of "Sun, 19 Apr 2015 19:35:16 +0200")
joakim@verona.se writes:
> I just created a new job for make check. That way you can see if the
> tests fail, and if master builds separately. That should be good enough
> until the tests work again? I mean, if the tests are broken, they are
> broken, and its better to know that than to suppress the breakage, right?
Yes. However, things are a little bit stalled. I've started with
vc-tests.el last automn on request of Eric Raymond. I don't know the innards
of vc-*.el that I could do serious bug fixing, I have just fixed some
simple cases.
Now I'm waiting until Eric could spend more time on this.
> You can have an account if you like. I think the "sign up" function is
> supposed to work I think.
Thanks. Likely, it is not urgent. With hydra I'm happy to follow the
messages on emacs-buildstatus@gnu.org. If you could configure Jenkins
that it sends also messages on *changed* result status it would be
great. I don't know who runs this mailing list, maybe Glenn Morris?
Best regards, Michael.
next prev parent reply other threads:[~2015-04-19 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 10:46 Another Emacs build-server joakim
2015-04-19 12:44 ` Dmitry Gutov
2015-04-19 15:50 ` joakim
2015-04-19 16:58 ` Michael Albinus
2015-04-19 17:35 ` joakim
2015-04-19 17:51 ` Michael Albinus [this message]
2015-04-19 20:15 ` joakim
2015-04-19 20:15 ` joakim
2015-04-19 17:37 ` Dmitry Gutov
2015-04-19 17:53 ` Michael Albinus
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=87a8y49fcg.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.