From: Toon Claes <toon@iotcl.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Ted Zlatanov <tzz@lifelogs.com>,
Michael Albinus <michael.albinus@gmx.de>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: EMBA builds failing
Date: Tue, 16 Apr 2019 09:07:21 +0200 [thread overview]
Message-ID: <87k1fua0nq.fsf@iotcl.com> (raw)
In-Reply-To: <c27a775d-56ab-a3e5-28dc-19cf900b4d50@yandex.ru> (Dmitry Gutov's message of "Thu, 11 Apr 2019 16:20:01 +0300")
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
I have again applied the patch so the email gives a direct link to the
raw log file.
I've also started working on the change in GitLab itself, so this patch
is no longer needed, see
https://gitlab.com/gitlab-org/gitlab-ce/issues/56849
Hopefully we'll get this change deployed in a month or so.
But I couldn't figure out why we always needed to reapply this patch?
Ted, have you been doing updates of GitLab? Or does it do it
automatically? Cause I see it runs 11.9.7 now, while we initially
deployed 11.1.4.
-- Toon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-04-16 7:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 23:57 EMBA builds failing Dmitry Gutov
2019-04-04 6:40 ` Michael Albinus
2019-04-11 13:20 ` Dmitry Gutov
2019-04-11 13:26 ` Toon Claes
2019-04-11 13:31 ` Michael Albinus
2019-04-11 19:28 ` Toon Claes
2019-04-11 13:36 ` Dmitry Gutov
2019-04-16 7:07 ` Toon Claes [this message]
2019-04-16 9:24 ` Michael Albinus
2019-04-19 19:29 ` Toon Claes
2019-04-19 19:34 ` Michael Albinus
2019-04-20 9:16 ` Robert Pluim
2019-04-20 14:57 ` Paul Eggert
2019-04-20 19:18 ` Michael Albinus
2019-04-19 23:10 ` Dmitry Gutov
2019-04-23 10:21 ` Toon Claes
2019-04-22 20:36 ` Michael Albinus
2019-04-23 10:09 ` Toon Claes
2019-04-23 12:57 ` 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
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=87k1fua0nq.fsf@iotcl.com \
--to=toon@iotcl.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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.
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).