From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages
Date: Sun, 6 Dec 2015 18:49:12 +0100 [thread overview]
Message-ID: <201512061849.15510.dilfridge@gentoo.org> (raw)
In-Reply-To: <20151206174900.554900ca.mgorny@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Am Sonntag, 6. Dezember 2015, 17:49:00 schrieb Michał Górny:
> On Sun, 6 Dec 2015 11:09:48 -0500
>
> Michael Orlitzky <mjo@gentoo.org> wrote:
> > On 12/06/2015 11:00 AM, Michał Górny wrote:
> > >> Of course. Add the commit author, too: I want to know if I break
> > >> someone else's package.
> > >
> > > So far, can't do that since we don't know which commit exactly broke. I
> > > don't want to do any heuristics that could blame the wrong person.
> >
> > Is the testing performed per-push rather than per-commit? Either way, I
> > would like to get a notification that something broke, even if it wasn't
> > my commit at fault. Just change the word "blame" to "alert" so no one
> > feels slandered.
>
> It is done every 20 minutes, and takes around 7-10 minutes.
How about just adding everyone who pushed in that timeframe?
- --
Andreas K. Huettel
Gentoo Linux developer (council, perl, libreoffice)
dilfridge@gentoo.org
http://www.akhuettel.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWZHUYAAoJEHRrah2soMK+WwEQAM3kIuB898xKOXhYRkCWxZKP
UeXyqHWfUOuSoFwmNKwfOiHV7bJfAOMgKI6dymqFRjOU32gOMe2hSeR4W5E7ytT3
ykTjDO1zf+YmZ4Pn4xeXUa4f/SwqeD9exNl3O8+9wbMSd1CfQj1RL1YRQPjuDfsY
zZFbk7WBrkHVlIyUpiwE/3/CF4fCzg2FIDQdQv78p8MvEAEUz2JFolyaCAJzroje
TaAweY2oFC9e2aMfg2dtW2m85q/B1ZtYZzNVvCM+5iDRwbVZyNzttvb31GbQwRLO
yz5SJQqTk0TpoFXomq7hK0xb/leRnbbwjOC02sebMxP6Dw3ya33zeXG64gzEkYUB
7FrLo3U7jTWx+vepACJPOfULqtBP0u0YtFOzPdEHJbtv1qzGRXeSMctMvaS3XnBl
NFceqTxt19qiRu3zN3cpjuf/C0FhthAplooQfRD8quy7KLgM8gO8fuX6g706qXUJ
1QS2UXAyVVrHUDpU0fPM73Uts4RivaYyjSyiy1+neGPOVQ6TpkaSPgh2bjlsb7d8
gmM5s8Y8RmXi8LOGEr1w8cuiCTaFVlRgNQB3WAYpLQ/m/kDNakIAFlX4KhVZdBYh
n15BMUGJRfz1r/XYUXd89iwesjye0YGtww2TVWSpLkeZDInua+JhRy/30HaPuJ6O
LHJon3GqAM8fmjcZOa7N
=0QHR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-06 17:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 14:36 [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages Michał Górny
2015-12-06 14:54 ` Dirkjan Ochtman
2015-12-06 15:31 ` Michael Orlitzky
2015-12-06 16:00 ` Michał Górny
2015-12-06 16:09 ` Michael Orlitzky
2015-12-06 16:49 ` Michał Górny
2015-12-06 17:25 ` Michael Orlitzky
2015-12-06 17:49 ` Andreas K. Huettel [this message]
2015-12-08 7:01 ` Michał Górny
2015-12-06 16:52 ` Rich Freeman
2015-12-06 17:26 ` Ian Stakenvicius
2015-12-06 18:58 ` Rich Freeman
2015-12-08 0:05 ` Alec Warner
2015-12-08 0:27 ` Rich Freeman
2015-12-08 2:19 ` Anthony G. Basile
2015-12-08 3:21 ` Rich Freeman
2015-12-08 6:59 ` Michał Górny
2015-12-08 19:11 ` Daniel Campbell
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=201512061849.15510.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox