all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: GitLab CI setup file in scratch/tzz/gitlab
Date: Sun, 30 Apr 2017 21:53:59 -0400	[thread overview]
Message-ID: <87y3uhjqa0.fsf@lifelogs.com> (raw)
In-Reply-To: 356742bb-967f-67c1-6a30-62e4d4e30102@yandex.ru

On Mon, 1 May 2017 02:55:16 +0300 Dmitry Gutov <dgutov@yandex.ru> wrote: 

DG> On 01.05.2017 1:19, Richard Stallman wrote:

>> Perhaps the FSF should find volunteers to set up a server to do CI for
>> GNU packages using the GitLab software.  Would that be useful?

DG> That has always been the idea, yes. We are only using the GitLab service to
DG> evaluate the features of GitLab the program.

Thank you for suggesting that, Richard. I've been asking for a machine
for months, see the emacs-devel and savannah-admins threads.

There should be no problem with switching to a FSF/GNU host for the CI
service, when and if such a host becomes available.

I don't think the choice of CI system matters, this is a necessary step
regardless.

Thanks
Ted




  reply	other threads:[~2017-05-01  1:53 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 18:45 GitLab CI setup file in scratch/tzz/gitlab Ted Zlatanov
2017-04-26 18:51 ` Eli Zaretskii
2017-04-26 20:55   ` dptd dptd
2017-04-27  5:01   ` Lars Brinkhoff
2017-04-27 14:23     ` Eli Zaretskii
2017-04-27 14:37       ` Dmitry Gutov
2017-04-27 14:59         ` Eli Zaretskii
2017-04-27 15:16           ` Dmitry Gutov
2017-04-28 21:33             ` Richard Stallman
2017-04-29  0:41               ` Ted Zlatanov
2017-04-29 15:58                 ` Richard Stallman
2017-04-29 17:44                   ` Dmitry Gutov
2017-04-30 22:19                     ` Richard Stallman
2017-04-30 23:55                       ` Dmitry Gutov
2017-05-01  1:53                         ` Ted Zlatanov [this message]
2017-05-01 15:54                         ` Richard Stallman
2017-05-02 12:42                           ` Richard Stallman
2017-05-03  0:06                           ` Dmitry Gutov
2017-05-03 19:15                             ` Richard Stallman
2017-05-14  2:25                               ` Ted Zlatanov
2017-05-15  1:44                                 ` Richard Stallman
2017-05-15 20:08                                   ` Ted Zlatanov
2017-05-18  1:12                                   ` Perry E. Metzger
2017-05-19  1:19                                     ` Richard Stallman
2017-05-19  1:53                                       ` Perry E. Metzger
2017-05-21  3:25                                         ` Richard Stallman
2017-05-21  3:49                                           ` Jean-Christophe Helary
2017-05-22 12:15                                             ` Richard Stallman
2017-05-21 15:19                                   ` Tino Calancha
2017-04-29 18:22                 ` Lars Brinkhoff
2017-04-29 21:11                   ` Ted Zlatanov
2017-04-30 22:20                   ` Richard Stallman
2017-04-29  1:29               ` Mike Gerwitz
2017-04-27 17:43       ` Lars Brinkhoff
2017-04-27 20:16         ` Dmitry Gutov
2017-04-27 20:42           ` Eli Zaretskii
2017-04-27 23:20             ` Dmitry Gutov
2017-04-28  6:49               ` Eli Zaretskii
2017-04-28  8:33                 ` Dmitry Gutov
2017-04-28  9:45                   ` Eli Zaretskii
2017-04-28  9:58                     ` Dmitry Gutov
2017-04-28 13:17                       ` Eli Zaretskii
2017-04-28 13:35                         ` Dmitry Gutov
2017-04-28 12:47                     ` Ted Zlatanov
2017-04-28 13:24                       ` Lars Brinkhoff
2017-04-28 14:16                         ` Ted Zlatanov
2017-04-27 20:27         ` Eli Zaretskii
2017-04-28 21:34       ` Richard Stallman
2017-04-27 16:16   ` Ted Zlatanov
2018-07-23 13:14     ` Tino Calancha
2018-07-27 13:48       ` Toon Claes

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=87y3uhjqa0.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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 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.