From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Ted Zlatanov <tzz@lifelogs.com>,
Michael Albinus <michael.albinus@gmx.de>,
dick.r.chiang@gmail.com, emacs-devel@gnu.org
Subject: Re: EMBA status
Date: Tue, 14 Sep 2021 13:17:36 +0200 [thread overview]
Message-ID: <87h7enwgmn.fsf@gnus.org> (raw)
In-Reply-To: <c47cba0d-f5ba-4db5-c7bd-8c81667d475a@yandex.ru> (Dmitry Gutov's message of "Mon, 13 Sep 2021 23:31:31 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 13.09.2021 16:09, Ted Zlatanov wrote:
>> I'm not sure how to resolve the wider problem of contributions that
>> break tests. It's easy to start sending blame-mails but it's equally
>> easy for people to ignore them.
But wasn't the problem here that all builds fail?
> It would be much harder to ignore them than when they are not sent.
>
> I don't we are allowed to send them, though. Not without some official
> degree of acceptance of EMBA. As the CI, at least.
I'm all for sending automatic mail from EMBA to the author of the
failing commit, but I guess it has to be more reliable first.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-14 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o890pn60.fsf@dick>
[not found] ` <ff897941-48ca-c3a8-4993-844ec4ae6bf6@yandex.ru>
[not found] ` <87y284o33g.fsf@gnus.org>
[not found] ` <54758131-0e0d-1c4e-bf99-b329688a1b8d@yandex.ru>
[not found] ` <8735qbmfqn.fsf@gnus.org>
2021-09-12 15:54 ` EMBA status (was: bug#50509: 28.0.50; [PATCH] elisp-mode-tests regression) Michael Albinus
2021-09-13 13:09 ` EMBA status Ted Zlatanov
2021-09-13 20:31 ` Dmitry Gutov
2021-09-14 11:17 ` Lars Ingebrigtsen [this message]
2021-09-14 15:25 ` Alan Third
2021-09-14 19:16 ` EMBA status, " Ted Zlatanov
2021-09-15 8:05 ` Lars Ingebrigtsen
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=87h7enwgmn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=dgutov@yandex.ru \
--cc=dick.r.chiang@gmail.com \
--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).