From: Toon Claes <toon@iotcl.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: EMBA (Emacs Gitlab CI build server) is now available
Date: Sat, 05 Jan 2019 09:01:01 +0100 [thread overview]
Message-ID: <87pntbcz42.fsf@iotcl.com> (raw)
In-Reply-To: <8736q863ms.fsf@gmx.de> (Michael Albinus's message of "Fri, 04 Jan 2019 12:52:59 +0100")
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
Michael Albinus <michael.albinus@gmx.de> writes:
> Wouldn't it be possible to move the emacs/emacs project visibility to
> "public"? By this, people w/o emba credentials could look on the
> results, and files like <https://emba.gnu.org/emacs/emacs/-/jobs/446/raw>
> could be accessed easily from within Emacs.
We plan to do so in the near future. There are some small things we want
to fix before we do that.
-- Toon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-01-05 8:01 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pntbcz42.fsf@iotcl.com \
--to=toon@iotcl.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.