From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Subject: Re: EMBA (Emacs Gitlab CI build server) is now *public* available
Date: Wed, 30 Jan 2019 11:00:30 +0100 [thread overview]
Message-ID: <874l9qmpmp.fsf@gmx.de> (raw)
In-Reply-To: <m2a7jipjfi.fsf@gmail.com> (Robert Pluim's message of "Wed, 30 Jan 2019 10:46:09 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> It looks pretty cool, however if I visit
> https://emba.gnu.org/emacs/emacs/activity , it looks like we should
> blame Ted for every breakage.
It's not a bug, it's a feature :-) I really appreciate this, given that
I have caused several breakages these days ...
> Would it be possible to display the commit authors there?
Don't know. Likely not, because it reflects the git clone on the emba
server itself, which is triggered with Ted's credentials.
However, if you follow the git commit ref links, you will see the
committer. And the mails to the buildstatus ML contain the real
committer as well.
> Robert
Best regards, Michael.
next prev parent reply other threads:[~2019-01-30 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 16:29 EMBA (Emacs Gitlab CI build server) is now available Ted Zlatanov
2018-12-31 17:54 ` Michael Albinus
2018-12-31 18:05 ` Ted Zlatanov
2019-01-01 12:08 ` Michael Albinus
2019-01-01 14:56 ` Ted Zlatanov
2019-01-01 16:51 ` Michael Albinus
2019-01-02 15:05 ` Justin Joseph Kaipada
2019-01-02 15:17 ` Michael Albinus
2019-01-04 11:52 ` Michael Albinus
2019-01-05 8:01 ` Toon Claes
2019-01-30 8:53 ` EMBA (Emacs Gitlab CI build server) is now *public* available Toon Claes
2019-01-30 9:46 ` Robert Pluim
2019-01-30 10:00 ` Michael Albinus [this message]
2019-01-30 11:23 ` Toon Claes
2019-01-30 12:13 ` Michael Albinus
2019-01-30 20:39 ` Ted Zlatanov
2019-02-05 12:50 ` Robert Pluim
2019-02-05 12:55 ` Michael Albinus
2019-02-05 14:58 ` Robert Pluim
2019-02-05 15:42 ` Ted Zlatanov
2019-02-05 15:50 ` Robert Pluim
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=874l9qmpmp.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.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.
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).