From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lars@nocrew.org, emacs-devel@gnu.org
Subject: Re: GitLab CI setup file in scratch/tzz/gitlab
Date: Thu, 27 Apr 2017 18:16:34 +0300 [thread overview]
Message-ID: <c1eebb33-e52a-fd67-f95b-c3bc415f7c4f@yandex.ru> (raw)
In-Reply-To: <837f25oq0d.fsf@gnu.org>
On 27.04.2017 17:59, Eli Zaretskii wrote:
>> It sounds silly. We should have an accessible, friendly CI instance for
>> all our users.
>
> I don't understand this attack. We didn't yet decide that this site
> will be our CI site.
If we don't like it, we can easily delete the file. It's low-conflict,
low-maintenance. There's almost zero cost to adding it.
Further, the contents of the file are not tied to the "site", just to
GitLab as a project. It can be used by other GitLab installations
without changes.
> Until we do, why should we function as someone
> else's repository??
From that perspective, Ted has already done what you're asking
(committed the change into a different repository).
The first message of this thread is a request to take a further step, to
make a fair evaluation easier.
As a result of having this file in master, the GitLab instance will
build all later branches that are pushed to the repository (with some
possible exceptions).
I am restating here the second paragraph of that email, BTW.
next prev parent reply other threads:[~2017-04-27 15:16 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 [this message]
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
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
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=c1eebb33-e52a-fd67-f95b-c3bc415f7c4f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lars@nocrew.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).