From: Lars Schneider <larsxschneider@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Duy Nguyen" <pclouds@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Jiang Xin" <worldhello.net@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [BUG] test suite broken with GETTEXT_POISON=YesPlease
Date: Tue, 25 Apr 2017 10:51:20 +0200 [thread overview]
Message-ID: <054E67A2-56B0-4C91-89F5-F33E8C00ED61@gmail.com> (raw)
In-Reply-To: <20170424203710.cijg3bjdrb2eywmh@sigill.intra.peff.net>
> On 24 Apr 2017, at 22:37, Jeff King <peff@peff.net> wrote:
>
> On Mon, Apr 24, 2017 at 08:22:36PM +0700, Duy Nguyen wrote:
>
>> Off topic, is it possible to receive mail notifications from Travis
>> when a fault is found in either 'pu', 'next' or 'master'? I know how
>> to do it in Jenkins, but I'm not familiar with Travis and there's no
>> obvious button from the web page..
>
> I looked into this a bit for my personal builds. Notification config has
> to go into the .travis.yml file[1]. So I think the best we could do is
> send a notification email to some mailing list, and then let people
> subscribe to that (or it could go to git@vger; I don't know how noisy it
> would be).
A separate mailing list sounds like a very good idea to me!
Maybe "git-builds@vger.kernel.org" or something?
What would it take to set something up like this?
- Lars
next prev parent reply other threads:[~2017-04-25 8:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 21:58 [BUG] test suite broken with GETTEXT_POISON=YesPlease Ævar Arnfjörð Bjarmason
2017-04-21 14:47 ` Michael J Gruber
2017-04-21 17:28 ` Ævar Arnfjörð Bjarmason
2017-04-24 1:18 ` Junio C Hamano
[not found] ` <20170424110434.27689-1-avarab@gmail.com>
2017-04-26 9:17 ` [PATCH] tests: remove the GETTEXT_POISON compile-time option to test i18n marking Michael J Gruber
2017-04-26 14:27 ` Ævar Arnfjörð Bjarmason
2017-04-21 14:54 ` [BUG] test suite broken with GETTEXT_POISON=YesPlease Lars Schneider
2017-04-21 18:05 ` Ævar Arnfjörð Bjarmason
2017-04-21 18:57 ` [PATCH] tests: fix tests broken under GETTEXT_POISON=YesPlease Ævar Arnfjörð Bjarmason
2017-04-24 1:15 ` Junio C Hamano
2017-04-24 8:18 ` Ævar Arnfjörð Bjarmason
2017-04-25 4:11 ` Junio C Hamano
2017-04-25 8:56 ` Ævar Arnfjörð Bjarmason
2017-04-26 1:58 ` Junio C Hamano
2017-04-26 7:56 ` Ævar Arnfjörð Bjarmason
2017-04-24 13:22 ` [BUG] test suite broken with GETTEXT_POISON=YesPlease Duy Nguyen
2017-04-24 20:37 ` Jeff King
2017-04-25 8:51 ` Lars Schneider [this message]
2017-04-25 10:01 ` Jeff King
2017-04-28 8:42 ` Lars Schneider
2017-04-28 8:44 ` Jeff King
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=054E67A2-56B0-4C91-89F5-F33E8C00ED61@gmail.com \
--to=larsxschneider@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=worldhello.net@gmail.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://80x24.org/mirrors/git.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).